-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.
Steps to reproduce
- Login to JIRA as an Administrator;
- Create an Epic in a project;
- Now create a new issues and choose a different project;
- Click on the dropdown of the "Epic Link" field;
- The Epic created before in a different project is listed in this project as well;
What is needed
We want the "Epic Link" field to display only Epics from the selected project.
- duplicates
-
JSWCLOUD-12611 The EPic Link field lists Epics that are outside of the Project I am working on
-
- Closed
-
- is related to
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Under Consideration
[JSWCLOUD-12016] The "Epic Link" field list Epics from all the projects instead of the current one
For any hardened Project Management individual it is ridiculous this feature cannot be done oput to a "community vote". The good news is other project management systems do offer what the hegemonic (bloated) billion dollar company refuses to see its own errors.
When creating new projects that have different epics, its ludicrous that development teams see epics from previous projects. To those expert consultants imagine developing a software development project in high end video games around Racing. A racing video game. Its completed using Jira. Next the 30man team makes an Ice Hockey game for 2 years, again using Jira. They go onto a new Kanban or Scrum board and in between making new epics for their ice hockey game they see a sea of "Silverstone racing track" "Brands Hatch" "Melbourne Racetrack" "Nurburgring" "San Marino Grand Prix" as epics, that they dont want on this project and cant delete when linking epics on their new ice hockey game.
Ridiculous. Other Project Management systems usually let you start a "new project" fresh or "import template" from old projects giving you fields you want to cross over.
Atlassian has now told me that we need to vote for this issue instead (related): https://jira.atlassian.com/browse/JSWCLOUD-21180
Well, that hasn’t been fixed until now? Raised in 2014! Seriously!
This seems to be a logical and structural flow issue. I have been learning and testing out Jira Standard Package for my company for well over a month and came across to this issue as well. Adding more projects and it's getting bigger and mixed up. We are planning to implement Jira in phases.
For example Simplest logical example
I am building a software product Orange called Project Orange,
I am building another software product Apple called Project Apple
I have created EPICs for both of these projects
And now I am building another software product Watermelon and created epic for this as well
While adding stories or tasks or bugs etc related to either of the projects, all of them are showing down to the drop down list. The case is not limited only to EPIC but it also goes to sprints as well across all issue types. Stories, Tasks, Bugs, and EPIC it self [In epic’s case, sprints from other projects are showing down to the drop-down list.
When creating an issue [Any-type] from within the given project and UI picks up the project name automatically then why we can not sort this EPIC, Sprint Fields acting as General drop-down Fields rather than specific? As general public/community feedback, we do understand change is multidimensional but still, this would be one of the great improvements to this product.
Jira Team, kindly anticipate and consider this change as a potential improvement while enjoying all those healthiest foods Oranges, Apples, and Watermelons.
If there is no issue with the case mentioned above, then please suggest & clarify the correct flow and usage.
Thank you