Modify the default hierarchy levels. By default, Jira is set up with 3 levels of issue type hierarchy: Epic (level 1), Story (level 0) and Sub-Task (level -1). You can modify these levels to better reflect how your teams work. Hi @Fred van Beek. With regards your CSV import, With Epic, please use the epic link field as the parent/child fields are reserved for Task -> sub-task association. As you are bot the admin, make sure you can create and associate the issues from the Jira project’s create issue screen first else your import will potentially fail.
Answer accepted. I was able to use Automation for Jira today for my use case, which was to change the color of the Epic when a specific custom field (SoW Signed) was changed to "Yes." I discovered that there was already a custom field called "Epic Color" and I found the color codes online. Yes, this would be the preferred solution now.
Within JXL, enable the issue hierarchy. This is a one click action. You can now easily select the epics and their children (just like you would select cells or rows in Excel/Google Sheets), right-click them, and invoke the "bulk edit" process via the context menu. This is how this would look in action: (In the future, we may add a "move
In Jira, Epic links aren't "normal" issue links so that's why your "linked issue match" doesn't match anything. You'll need to use the "JQL issues" drop down and enter: "Epic Link" = { {issue.key}} as the "Related issues JQL", before entering the appropriate statuses. (see image below) Hope that helps! Cheers, Mark C.
A subtask always belongs to its parent, and that parent can have an Epic, which then implies that the sub-task is inside that Epic. But there's an oversight in that the subtasks don't actually inherit the information internally. There are open issues which Atlassian have accepted to get this design flaw fixed.
There's two parts to this. It's absolutely correct that a sub-task should not be assigned to an Epic. A sub-task belongs to a parent, and hence belong to an Epic via that. It's absolutely a howling bug or flaw in JIRA that sub-tasks do not behave as though they belong to the same Epic as their parent. Yes, a few times I've scripted a field that
To enable ranking: Go to your board, then select more ( ) > Configure board. Click the Add Rank button. The filter for your board will be updated to order by Rank. This will affect all boards using this filter. 1 ORDER BY Rank ASC. You can also rank issues by other issue properties — for example, priority or issuetype:
1 answer. If you go on the project settings and look at the screens associated with the issue type you are referring to, check that on the 'edit' screen the epic link field is there, then you should be allowed to change it from the view screen. I already have the input to change the epic link but the tooltip does not autocomplete with existing
\n\n\n \n\n\n\n\njira change epic to task
uwLC0dr.
  • gvfjo3w9mo.pages.dev/156
  • gvfjo3w9mo.pages.dev/12
  • gvfjo3w9mo.pages.dev/290
  • gvfjo3w9mo.pages.dev/271
  • gvfjo3w9mo.pages.dev/389
  • gvfjo3w9mo.pages.dev/434
  • gvfjo3w9mo.pages.dev/164
  • gvfjo3w9mo.pages.dev/342

    • jira change epic to task