If it's the transition in the epic (e.g. prevent closing the epic if the issue in the epic are open), you'll be better off use the "epicLinkManager". Something like this: import com.onresolve.scriptrunner.runner.customisers.JiraAgileBean. import com.onresolve.scriptrunner.runner.customisers.WithPlugin. @WithPlugin ("com.pyxis.greenhopper.jira")
There are three ways to export issues from Jira following this route: 3.1. Reactivate the Excel export option from the Jira menu. This option allows the Excel export option available from the Exports drop-down menu. Note, the "Excel document" that Jira will export is an HTML document that can be outdated at any moment.
From your project’s sidebar, select Project settings > Issues > Layout. Select an issue layout. Select Copy issue layout in the top right. Only Jira admins can see this button. Choose which screen’s layout you want to copy, then the projects you want to apply it to. The projects available will be those that use the same screen as the layout
4 days ago · Start using filters to search for Jira issues: Create a new Confluence page or edit an existing one. Type /jira and select Jira issues. With Basic selected, use the filters to search by Project, Type, Status, or Assignee. Select Insert issues. This will display your selected issues in a table format you can interact with. To edit your table of
Follow the steps below to Link Epic to a Story. Click on “ Create ” (at top-middle) > Set Issue Type to “ Epic ” > Enter Epic Name and Summary > Click on “ Create ” >. Now, Go to a Story to link > Click on “ Show 6 more fields ” (right-side) > Select “ To Link to a Story ” in Epic Link field. How to Link Epic to a Story With that said, I created my 1st automation rule that adds a parent/child Link Type (as automation for Jira currently isn’t supporting advanced issue linking past the Epic level) once the ‘Parent Link’ field is populated on an Epic. Next, I have a 2nd automation rule that I’m trying to configure following this logic: R3BwR7. 963258413371887186359472
