To do this: Select Settings > Issues > Issue type hierarchy. Click the level name that you want to rename. Edit the level name, and select Save changes. Please note that these updated level names may appear throughout your Jira experience, including: the Type column on the Issue Types settings page.
Once all subtasks had been converted into tasks, enter the task that you'd like to convert into an epic and click on More > Move. Leave the project unchanged and just change the type from task to epic. Finally, associate the tasks with the epic. Kelly Johnson Jul 30, 2017. Obviouslly you can manually, painstakingly do all these things.

Actually, you would need to set a parameter in a JQL filter to set the order of the child issues in the Epics and display it using the filter results gadget. Let me give you an example: Let's suppose you want to display all issues under the Epic "test-1" ordered by the creation date. These would be the steps: 1 - Create the following JQL filter:

I think you then create a rule with Issue transitioned as trigger, a Branch rule / related issues with the EPIC and below that a create issue action. See also the screenshot. And then of course expand with conditions. Does this point you in the right direction? Regards, Marco Answer accepted. You are missing a line to actually change the value on the issue. linkedIssueObj.setCustomFieldValue (accountField, issue.getCustomFieldValue (accountField) ) But note that this will not cause your linkedIssue to show the history of that change.
Probably something like issue.epic=your epic. Then you add your script, where you recover alll the issues linked to the epic, and check their status. Create your logic so that if everithing is as it should be, you just change the status, using MutableIssue object.
\n\n \n jira change issue to epic
The first sprint shown is the one that contains the first issue (in the epic) that transitions out of the 'To Do' status, i.e. work is started on the epic. The last sprint shown is the one when all work is completed for the epic; or if work remains, then the predicted sprint when work will be finished. The mapping of statuses to your board
Here is a search from the Marketplace: Once you have that field and fill it with the Epic issue key you desire, you would use the Automation for Jira native feature to copy that data from that field to the Epic Link field. Note this will work only in Company Managed projects. If you are using a Team Managed project, those don't use the Epic
You can set the Epic Color for an Epic in a Business project, using the Bulk Change feature to edit the field. The color will display in the Child issues where Epic Link is shown. If what you're showing on that card is the Epic Link field, then it should show there also.
If I go to one of my stories that is not currently attached to an epic and I click the "show more" link then I see Epic Link none. I can then edit and change none to the desired Epic Name. If it isn't there then you need to go to project settings > Issue Layout and edit the layout associated w/ story.
Rising Star. Dec 19, 2017. Hi, I am trying to set the Epic link of an issue that is created with the clone an issue and link script from ScriptRunner. I have the following script in a post-function in the additional actions field: import com.onresolve.scriptrunner.runner.util.UserMessageUtil. import com.atlassian.jira.component.ComponentAccessor.
.
  • woa4dm9fqs.pages.dev/117
  • woa4dm9fqs.pages.dev/16
  • woa4dm9fqs.pages.dev/477
  • woa4dm9fqs.pages.dev/305
  • woa4dm9fqs.pages.dev/448
  • woa4dm9fqs.pages.dev/465
  • woa4dm9fqs.pages.dev/361
  • woa4dm9fqs.pages.dev/287

    • jira change issue to epic