-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
2
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Within JIRA Portfolio Epics can be associated with an Initiative.
You can also create JIRA issues linked to the Initiatives within Portfolio.
The Epics in Portfolio can also be associated with JIRA issues of type Epic.
When you link a JIRA issue with an Initiative this should create a link between the Issue and the Epic JIRA issues which implement that Initiative.
For example
- Initiative = Mars Mission (JIRA issue SPACE-100) – is implemented by
- Epic = Space Craft Build (JIRA issue SPACE-200)
- Epic = Catering (JIRA issue SPACE-250)
If you open up issue SPACE-100 you would see an issue link pointing at SPACE-200 and SPACE-250 and the corresponding counter-links would appear on those issues as well.
This will increase the traceability and visibility of the Initiatives and also allow JQL queries to be constructed which can then be used in regular JIRA issue navigator based reporting. For example – something like:
issuetype = Initiative AND summary = "Mars Mission" AND status NOT IN (Resolved, Closed) AND NOT (issueFunction IN linkedIssuesOf("status != Closed", "implements")
Would show you all of the outstanding Epics required to implement the Mars Mission initiative.
- relates to
-
- Closed
-
- Closed
- links to
[JSWSERVER-25148] JIRA issues associated with Initiatives should link to the implementing Epics
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | Original: Plan-Roadmap ril | New: Plan-Roadmap cleanup-seos-fy25 ril |
| Labels | Original: Plan-Roadmap | New: Plan-Roadmap ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979644 ] |
| Component/s | Original: Integration [ 47600 ] | |
| Component/s | New: (Advanced Roadmaps) Plan - Roadmap [ 63498 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Advanced Roadmaps [ 16510 ] | New: Jira Software Server and Data Center [ 12200 ] |
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
| Labels | Original: jpos_1021 jpos_1026 | New: Plan-Roadmap |
| UIS | Original: 8 | New: 0 |
| UIS | Original: 7 | New: 8 |
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center