Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-12016

The "Epic Link" field list Epics from all the projects instead of the current one

XMLWordPrintable

    • Hide
      Atlassian Status as at 11 February 2016

      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 below for discussion 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

      Show
      Atlassian Status as at 11 February 2016 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 below for discussion 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
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      Steps to reproduce

      1. Login to JIRA as an Administrator;
      2. Create an Epic in a project;
      3. Now create a new issues and choose a different project;
      4. Click on the dropdown of the "Epic Link" field;
      5. 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.

        1. e03-1.png
          e03-1.png
          98 kB
        2. e03-2.png
          e03-2.png
          100 kB
        3. e03-3.png
          e03-3.png
          96 kB
        4. Screen Shot 2015-11-18 at 23.14.41.png
          Screen Shot 2015-11-18 at 23.14.41.png
          49 kB

          Form Name

            [JSWSERVER-12016] The "Epic Link" field list Epics from all the projects instead of the current one

            Shane Giroux added a comment -

            This is a big issue. I understand a board may cross multiple projects but an issue is made for a Project, not for a board, no? This could turf a move to Jira for us as we work on dozens and dozens of projects.

            Shane Giroux added a comment - This is a big issue. I understand a board may cross multiple projects but an issue is made for a Project, not for a board, no? This could turf a move to Jira for us as we work on dozens and dozens of projects.

            Matt Shedlov added a comment -

            Dear Atlassian Jira Support, on behalf of Boston Scientific and all our Jira instances worldwide, please provide an admin setting to only display Epics created within a specific project.  Epics created from other projects should not be displayed - this makes no sense as teams want to have fast and efficient display of their Epics (created within their project) only.  

            Matt Shedlov added a comment - Dear Atlassian Jira Support, on behalf of Boston Scientific and all our Jira instances worldwide, please provide an admin setting to only display Epics created within a specific project.  Epics created from other projects should not be displayed - this makes no sense as teams want to have fast and efficient display of their Epics (created within their project) only.  

            David Dominguez Admin added a comment -

            I would like no Epics from other projects in mine, it could be good to have a different "context" to limit this depending on the project.

            Looking forward to getting a solution finally, it seems this this is something requested since 6 years.

            Thanks.

            David Dominguez Admin added a comment - I would like no Epics from other projects in mine, it could be good to have a different "context" to limit this depending on the project. Looking forward to getting a solution finally, it seems this this is something requested since 6 years. Thanks.

            Zafrir Yerushalmi added a comment -

            Still not resolved... is there a plan to resolve it?

            Zafrir Yerushalmi added a comment - Still not resolved... is there a plan to resolve it?

            Kamenkov Kirill added a comment -

            Yes, it can. I also want to have the opportunity to narrow down the epic list. But not to the same project. A better option is to add a JQL filter.
            Don't forget that epics and tasks can be placed in different Jira projects.

            Kamenkov Kirill added a comment - Yes, it can. I also want to have the opportunity to narrow down the epic list. But not to the same project. A better option is to add a JQL filter. Don't forget that epics and tasks can be placed in different Jira projects.

            Vathenbala BALASUBRAMANIAM added a comment -

            epics can definitely vary from one project to another. 

            When you have several projects it comes very difficult to differentiate epics. We have exactly same issue on Labels...

            The question is more why can't we scope epics and labels by project.

            Vathenbala BALASUBRAMANIAM added a comment - epics can definitely vary from one project to another.  When you have several projects it comes very difficult to differentiate epics. We have exactly same issue on Labels... The question is more why can't we scope epics and labels by project.

            Kamenkov Kirill added a comment -

            It's not a bug. Why can't epics be stored in another project?

            Kamenkov Kirill added a comment - It's not a bug. Why can't epics be stored in another project?

            Hydra added a comment -

            Issue still exists in the Jira cloud. It really doesn't make sense to have this.

            Hydra added a comment - Issue still exists in the Jira cloud. It really doesn't make sense to have this.

            Dasha added a comment -

            It's not solved.

            Dasha added a comment - It's not solved.

            Santhosh Kadathala added a comment -

            Hi,
            we are on Jira software 8.13.0, recently we are upgraded from 7.13.8 to 8.13.0, we have two projects A and B A is having issue type Bug with Epic field, B is the project with restricted only Epics, In A project Users doesn't have permission any sort of Activities for Project B, but when issue creating in project A users are able to see in Epic Search field of Project B Epics, How can they can able to see the Epics links even we restricted to see the epics.

            why Jira allows you to see and select epics that you do not have permission for I’ll never understand.

            Can anyone help me out how to restrict the epics in Search box epic link.

            Thanks.

            Santhosh Kadathala added a comment - Hi, we are on Jira software 8.13.0, recently we are upgraded from 7.13.8 to 8.13.0, we have two projects A and B A is having issue type Bug with Epic field, B is the project with restricted only Epics, In A project Users doesn't have permission any sort of Activities for Project B, but when issue creating in project A users are able to see in Epic Search field of Project B Epics, How can they can able to see the Epics links even we restricted to see the epics. why Jira allows you to see and select epics that you do not have permission for I’ll never understand. Can anyone help me out how to restrict the epics in Search box epic link. Thanks.

              Unassigned Unassigned
              pschaff Pietro Schaff (Inactive)
              Votes:
              218 Vote for this issue
              Watchers:
              199 Start watching this issue

                Created:
                Updated:
                Resolved: