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

+1 for voted for it

Atlassian has now told me that we need to vote for this issue instead (related): https://jira.atlassian.com/browse/JSWCLOUD-21180

+1 for not fixed.

+1 for not fixed!

+1 for not fixed - Jira Cloud.

And still not fixed.

+1 for "not fixed"

any news about this issue? thanks

This is not fixed

Not fixed at all! 

This is still an issue.

I don't see this as a fix, more a  hack! You should have the option to hide epics from other projects from users in the drop down . I don't want my team seeing epics on projects they don't work on! Even if they don't have the permissions it appears a user can still see an epics in the drop down from another other project.

Me too.

I am also facing the same issue.

Hi Kim,

If you are still experiencing the issue, please raise a support request at https://support.atlassian.com

Cheers,
Ignat
JIRA Bugmaster.

I see that there the epics from the current project are displayed then there is a separator and then all epics from all projects are displayed.  How do I remove that second part of the drop down?

Either I am still having this bug or I did not configure permissions correctly. Can you give me directions how to configure Jira so the projects can not share any Epics between those? I am using Jira Cloud Code.

I still see epics from other projects in my Cloud Instance.

Our Use Case is that we link to Epics that are in another project. Is there a way to get epics from another project in the dropdown (e.g. a project setting)? Perhaps show all matching epics if there are fewer than 10? Or a checkbox that you can click on that displays all results (like the closed epics checkbox)?

prabier7658304 - I've fixed the links up now, thanks.

Thanks Martin. Your link "…comment above…" works but the previous one "… (comment-820661)…" doesn't display the answer. Anyway, thanks for your answer.

prabier7658304 - as per my previous comment, we have implemented a solution which addresses the required use-cases and is optimised for the main use-case of locating an open epic from the same project, the comment above details the implementation.

Kind regards,
Martin
JIRA Software

We have installed the version 7.1.0, I read the server release notes and I still see all the Epics from all projects when I create a new issue…
What am I missing?

We have implemented a solution which addresses the required use-cases and is optimised for the main use-case of locating an open epic from the same project, see comment above for more on the implementation.

This feature is now available for both JIRA Software Cloud and JIRA Software Server.
The server release version is 7.1.0, please see the server release notes for further details.

Kind regards,
Martin
JIRA Software

edit: fixed URL

krao1 - not yet, it will be available in the next major release of JIRA Software for server.
Kind regards,
Martin
JIRA Software

Is this available in the Jira software for server install ?

heather.walden1362015929 - this should be visible in your Cloud instance now.
Sprint selection is not covered in this issue, please see https://jira.atlassian.com/browse/GHS-11814

Kind regards,
Martin
JIRA Software

I am not seeing this updated in our cloud yet and I also see this issue when selecting a sprint. Separate issue or same?

Thanks Martin! This is very helpful and it's ALWAYS great to see issues that impact a lot of people getting fixed! I know we all appreciate it.

This is now available in JIRA Software Cloud and will be available for JIRA Software Server in a forthcoming release.
Kind regards,
Martin
JIRA Software

ivan.zaguirre1499704428 - it's not shipped yet, please continue to watch this issue for updates of the fix version for JIRA Software Cloud and JIRA Software Server. I will also update the Current Status field when it's released.
The release to JIRA Software Cloud is expected soon.

Kind regards
Martin
JIRA Software

Martin,
I've been checking my company JIRA version and it's 7.0

But I can't see the solution that you explained on comment-820661. Why?

zahira.melendez - the type-ahead currently limits the list to 10 items as you note. We will look into increasing the length of this list balancing performance and usability concerns.

Kind regards,
Martin
JIRA Software

Will the type-ahead display all the epics? Currently in v6.3.12 the type-ahead limits the list to 10. For example, I have a project that has 21 epics. When I type-ahead the project key "SR", the drop down displays 10 of those epics. If my epic is not listed and I don't remember the name of the epic, how do I get it? Displaying all the matches or having a "View all" link like the Component field is beneficial.

Thanks for addressing this issue.

huuuze, this will be available for a future release of JIRA Software only (so 7.x).

Versions of JIRA before 7 (using JIRA Agile) will not get this update, an upgrade to a newer version would be required.

No new versions of JIRA Agile will be released, the only exception would be in case of a security fix. Only critical security issues are backported as per the guidelines set out in the security policy at https://www.atlassian.com/security/secpol with further information at https://confluence.atlassian.com/support/atlassian-patch-policy-201852333.html

Kind regards
Martin
JIRA Software

@Martin, I agree with Cody – this solution is an improvement.

Will the solution to this problem be applied to the 6.x releases or only 7.x?

@Martin - Your proposed solution is a definite improvement. Thanks!

rob.geraedts - I have explained comment-820661 why this is possible and how it may be used. The shortest summary is that Agile boards show all epics returned by the board's filter and any can be used as the team sees fit. Cross-project or multiple project boards are one common scenario.
More information about the boards is available at https://confluence.atlassian.com/display/JIRASOFTWARECLOUD/Creating+a+board

I've not been actively monitoring this issue so forgive me if I overlook something. I'm not getting the point regarding the Sprint board being able to show issues from more than one project.
If I create an issue, I first select a project to create it in. After selecting a project, I cannot understand how/why I should be able to attach the issue to an epic that is created in another project.

Consider Project A with Epic A and Project B with Epic B.
In my opinion I should never be able to create an issue X that is related to Project A and Epic B! This simply doesn't make sense to me.

Am I missing something?

Rob.

huuuze - The list should only contain epics from projects which the user has browse permissions. As noted above, if you believe this not to be the case please create a support ticket at https://support.atlassian.com . That way we can provide you with support specific to your circumstances and with higher security.

@Martin, and the "Other epics" section will not include Epics if the user does not have permissions in that project, correct?

huuuze - Correct, relative to the issue being edited. Effectively Suggestions would be this project, Other epics would be other projects.
For a project with many open epics the Suggestions section would probably be the whole list at first, then on typing as the list is filtered it would depend on the matching. But the segregation would persist as seen in the 3rd image in my comment above.

@Martin, to be clear, the "Suggestions" section will only llist Epics associated with the ticket's project, correct?

rob.geraedts, karen.e.rogalski, huuuze - there are no known security issues with the epic link field, if a user does not have view permissions for a project then they will not see the epics for that project. If you believe this not to be the case please create a support ticket at https://support.atlassian.com . That way we can provide you with support specific to your circumstances and with higher security.

Kind regards
Martin
JIRA Software

I would like to clarify here that it is not a bug that epics outside of the current project can be used for issue assignment. Agile boards are highly configurable and support multiple projects. It is possible to use epics from one or more projects in the epic panel and assign issues from one or more projects to them - they do not need to be from the same project. This allows management and reporting of epics in single and cross-project cases i.e. progress on an epic with issues from multiple projects can be viewed on an epic report or epic burndown.

The Agile boards, which are the heart of Software projects, support these assignment options and so do the menus used in other contexts to edit the epic link for issues, including the menu in the Quick Create and Quick Edit dialogs and the menu in the View Issue page.

We understand that assignment in these additional contexts is problematic for many of you, the current implementation makes it difficult to identify an epic's project and also if the epic is still open or has been marked as done. We are working to improve this and I have recently updated a related Suggestion GHS-9993 with the solution we are working on which I will post here too.

This approach will assist with the primary goal of finding an open epic in the same project as the issue, but will still allow for the other secondary goals of finding open epics in other projects and done epics in both the same and other projects.

Show open epics only
When "Show done" is unchecked the menu will show:
Top section (if results exist) named Suggestions
Open epics from the same project as the issue (listed alphanumerically)
Second section (if results exist) named All epics
Open epics from other projects (listed alphanumerically)

Show open and done epics
When "Show done" is checked the menu will show:
Top section (if results exist) named Suggestions
Open and Done epics from the same project as the issue (listed alphanumerically, meta-data indicated if done)
Second section (if results exist) named All epics
Open and Done epics from other projects (listed alphanumerically, meta-data indicated if done)

The menu will still include a type-ahead control to filter the list by typing.

Kind regards
Martin
JIRA Software

@Brian, same problem can happen if you have security on issue level permission.

@Fabrizio, that makes sense if those projects are included in the same Agile board. However, this makes no sense as a default behavior. It also overrides the security settings within the project, allowing users to see the Epic name even though they don't have view permissions in that project.

It's a bug and, frankly, should be an easy one to fix from Atlassian's perspective. Add a filter to the Epic Link dropdown that determines if that epic's project is in the Agile board's filter and if security permissions would allow that user to view it.

I encourage everyone to vote this issue up.

for me and a lot of our contact, this is good as it is.
Usually we have different project that store epic that has to be shared in different software project

Not a Suggestion, this is a Bug for my large organization. Re-classify it as a Bug and fix it Atlassian!

She did when she created it:

https://jira.atlassian.com/browse/GHS-12611

But Atlassian closed it, declaring it a duplicate of this "Suggestion".