When: Manual Trigger. Select which group (s) the user (s) who will edit the Resolution field should belong to (for example: jira-administrators) Then: Edit issue fields. Choose Resolution as the field. Set the value to the value of your choice (for example Won't Do) The rule should look like in the screenshot below. What is changing? Atlassian is standardizing how we associate parent and child issues across Jira for company-managed and team-managed projects. This results in deprecation of the Epic Link and Parent Link custom fields in REST APIs and webhooks, as well as in some other related changes. Please refer to the detailed change list below: Change 1 (Jira public API): Endpoints: All API endpoints If the issue (Story, Feature, Epic) has the sprint updated after the sprint is closed, then the reports in Jira Align may not accurately reflect the reports. Changed issues after the sprint is closed may not show in the report for that sprint. When preparing to close sprints in Jira, you should remove or split unfinished stories and adjust Since the Epic issue is in a non-editable status (due to the property jira.permission.edit.denied in the Workflow Status), this operation fails: the Epic Link gets cleared without being set to a new value; Note that this issue does not only impact the bulk move operation, but also the move action from the Jira Issue View page: To add or change the issue sources of your plan: Select Plan settings from the left side navigation. Select Issue sources. You can select a project , board, or filter as the source of issues for your plan. If you’re adding a new issue source to a pre-existing plan, you’ll need to manually associate the team with the issue source to use
If you create an Epic task, and then from within the Epic you click "Create a child issue" you can link and create the child issue and it appears inside the Epic listed as a child issue and part of the hierarchy. However, in the "List" view, the child issue appears separated from the Epic. There is a little arrow toggle which when clicked
33wXk.
  • kloozeo76c.pages.dev/453
  • kloozeo76c.pages.dev/194
  • kloozeo76c.pages.dev/530
  • kloozeo76c.pages.dev/54
  • kloozeo76c.pages.dev/482
  • kloozeo76c.pages.dev/4
  • kloozeo76c.pages.dev/380
  • kloozeo76c.pages.dev/342

    • jira remove issue from epic