Choose Tools > Bulk Change (top-right of issue search page) Select the Epic (s) you wish to edit and choose Edit Issues as the operation. Search on this page for Epic Status and change it back to In Progress or To Do. Follow the rest of the screens to bulk-edit. Refresh your board. ^ This second option worked when I tested it - let me know if

set your condition. 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.

OPTION 2 - IF/Else Logic. If you don't have business logic that enables you to dynamically capture the epic, you could hard set it with If/Else conditions. For example: If Component = Component A. Issue Update Epic Link with . Else If Component = Component B. Issue Update Epic Link with . Else If Component = Component C.

The child issues themselves will sill exist, but the links between them won't. Suggested Solution. The process to convert between these projects should be able to maintain that relationship between epic and issues in that epic. Why this is important. Data is lost when converting due to this missing ability. Workaround. None

To allow various aspects of an issue to be assigned to different people. Navigate to an issue, and select more ( ••• ) > Create Sub-Task. Fill in the details as needed, and then click Create. Estimating issues in your backlog helps you to predict how long portions of the backlog might take to be delivered. You can check out the Issue Epic Gantt Chart in the eazyBI demo account. This report shows open epics and issues highlighting key metrics such as hours spent on issues within a given epic. Additionally, the issue epic Gantt chart report indicates story points for issues, the completion percentage, and the issue priority in the selected epic. aFg7i.
  • 3ty7zjv9os.pages.dev/287
  • 3ty7zjv9os.pages.dev/19
  • 3ty7zjv9os.pages.dev/392
  • 3ty7zjv9os.pages.dev/310
  • 3ty7zjv9os.pages.dev/265
  • 3ty7zjv9os.pages.dev/297
  • 3ty7zjv9os.pages.dev/245
  • 3ty7zjv9os.pages.dev/289
  • 3ty7zjv9os.pages.dev/139
  • jira convert issue to epic