Yes you can copy the values of fields in an Epic down to linked Tasks by using Automation for Jira. However, what type of project is it - Team-managed (Next-gen)? Or Company-managed (Classic Software)? Thank you - will check the solution ( Automation for Jira). You should be fine then with the Company-managed project.1 answer. Natively in Jira, the hierarchy is set to Epic -> Standard Issue Type -> Sub-task Issue Type. The 'Epic' Issue Type will always be at the top, with all other Issue Types being linked up to the Epic via the Epic Link field. Portfolio for Jira enables two things relevant to your issue; the ability to create custom hierarchies, such as "Epic Status" is indeed a locked down field, and generally not available for editing. My JIRA Admin and I figured out that by temporarily adding the "Epic Status" to the Epic's edit screen (which is an Admin only task, especially when the screen is shared amongst projects), a user with "Edit" permissions can then change the value.
First, change the issue type from "task" to "story". If they're configured the same way, then you can just edit the issue type directly, but if they're not, you'll need to use the "move" function to walk through all the checks that the data will be compatible with the Story config. Second, edit the "epic link" field - you'll be able to change
Meet the powerful Epic Progress gadget. There is an Epic Progress gadget, and it’s available thanks to Dashboard Hub for Jira. This gadget displays the progression in the completion of a particular group of epics by different estimation statistics. Get the insights you need with a well-designed user interface and great customization.
Hi @FR Jira Dev . First thing, you probably will want to perform a cascading change like this with two rules: epic change leads to updating the story/task/bug children; story/task/bug change leads to updating the sub-tasks. For this rule, ensure to set the option in the details for "Allow Rule Trigger", as this allows rule #1 to fire off rule #2
To make the trigger issue a child of the new epic, you will need to save the epic key and edit the trigger issue after your branch. I bolded the new sections, as shown below. trigger: issue created. action: re-fetch issue. condition: issue type is action: create a new Epic. action: create variable. name: varEpicKey.
The report shows data on the epic level: they automatically include logged hours and story points from epic's stories and sub-tasks. If you expand epics, you would see the linked story and sub-task issues and their respective values. Feel free to contact support@eazybi.com for furthers questions. Best, Ilze, eazyBI Customer Support Consultant
The epic remained in "back log" after moving the child issue @Mikael Sandberg. Okay, so try this. On the initial trigger component try and change the status it triggers on, I have noticed that if you use a rule from the library you have to change the default settings for the automation to trigger correctly.
1. if you use function. issueFunction in epicsOf ("status= 'In Progress'") as a result you will find get all Epics that have stories in status 'In Progress'. It is of no use in ScriptRunner JQL query condition because it doesn't test that one specific Epic linked with a Story. I tested it as a Condition on workflow transition and it doesn't
Tip: All sub-tasks need to be complete in order to close a sprint. If a sub-task is still open, but the parent issue could justifiably be closed (say, if the sub-task for updating documentation is still open but the functionality is good to go), you can change the sub-task into an issue and close your sprint. 9Vgt.jira change epic to task
