The use of ‘Epic Link’ is still allowed via JQL, but as has been described in the deprecation documentation, that is only so as to not break existing JQL queries that use it. The same applies to the UI… until the change-over is complete this year, as per this documentation and the new configuration starts being rolled out.
An epic is divided into smaller stories. Stories are then broken into manageable tasks. Epics may take several sprints or versions to complete. Epics are often associated with the Scrum management methodology. Epics and stories are not available in Jira Service Desk, so some users track new features suggested by customers as epics in Jira Software.
In Jira Software, issue hierarchy exists with Epics and Stories. Epics are used to track large pieces of work, and are broken down into smaller Stories. Portfolio for Jira lets you plan and track at each of these levels, with the Stories’ size (estimates) and progress rolling up to the Epic level.
If you use the "Epic Link", "epic", or "Parent Link" fields in Jira Automation’s smart values, you may be affected by this change. Atlassian plans to migrate the affected smart values by 31 May 2022 so that existing Automation rules won’t break, meaning you shouldn't need to make any changes on your side.
xn9t7mr. oopx1n6q7h.pages.dev/242oopx1n6q7h.pages.dev/199oopx1n6q7h.pages.dev/175oopx1n6q7h.pages.dev/82oopx1n6q7h.pages.dev/174oopx1n6q7h.pages.dev/324oopx1n6q7h.pages.dev/358oopx1n6q7h.pages.dev/48oopx1n6q7h.pages.dev/138
jira when to use epic
