As we’ve announced in Community, in company-managed project epics in Jira we’ll use Issue Color instead of Epic Color, and Summary instead of Epic Name. This is the current TMP behavior. Once we release this for company-managed projects in Jira, we encourage our partners to make a similar change. There is no deadline for it.
Understanding Epics, Stories, and Tasks in Jira: Epics: Epics represent large bodies of work that can be broken down into smaller, manageable pieces called Stories. They serve as high-level containers for related Stories and provide a comprehensive view of project progress and goals.
To get only issues linked using the "Epic-Story Link" link type, look for the ID on issuelinktype table and replace the 10101 I have at the very end. It was tested on postgres so you might need to tweak how to concat fields depending on your DB product. A bit of a glossary for the alias: PJP: project of the parent.
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.
1 accepted. to the best of my knowledge it is impossible to share components and versions across projects (globally). But labels can be used across the groups. considering your company structure; seems like you should only create one project in your Jira. If you do so; you can share components , versions and epics.
. 478 136 224 393 17 484 413 409
jira when to use epic
