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

    • 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

            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.

            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.  

            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.

            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?

            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.

            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.

            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.

            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.

            We are on Jira Software v 7.13. This still have been an issue.

            Since this ticket was closed (please re-open), other tickets have been logged for the same problem: JSWSERVER-16358 and JSWSERVER-20400. Unfortunately there is no response from Atlassian.

            Application Services added a comment - We are on Jira Software v 7.13. This still have been an issue. Since this ticket was closed (please re-open), other tickets have been logged for the same problem: JSWSERVER-16358 and  JSWSERVER-20400 . Unfortunately there is no response from Atlassian.

            We have the same problem as listed in this issue that is with resolution Fixed but it is not.

            Sverrir Tynes [Origo] added a comment - We have the same problem as listed in this issue that is with resolution Fixed but it is not.

            Same here.  Working for a company with 100s of projects and epics.  Epics field is now pretty much unusable.  Please fix.  A project-level setting to show only the current project's epics, please.

            Same with tags bytheway.

            tom_kluyskens added a comment - Same here.  Working for a company with 100s of projects and epics.  Epics field is now pretty much unusable.  Please fix.  A project-level setting to show only the current project's epics, please. Same with tags bytheway.

            still not resolved, please fix it on web version.

            Vathenbala BALASUBRAMANIAM added a comment - still not resolved, please fix it on web version.

            still not resolved, we need a solution for this. Thanks.

            jasminperalta added a comment - still not resolved, we need a solution for this. Thanks.

            Hi,

            @Jorden - the ticket status is Closed hence think everyone leaving comments (including myself) are wasting their time here. I've lost my faith in Atlassian after years of ignorance from their side... I'd not expect many of key issues awaiting response for years to be fixed soon or ever... they seem to prioritise UI touches first that guarantee increased sales instead of all those anoying issues in tickets that have been sitting untouched for years.

            David Sadowski added a comment - Hi, @Jorden - the ticket status is Closed hence think everyone leaving comments (including myself) are wasting their time here. I've lost my faith in Atlassian after years of ignorance from their side... I'd not expect many of key issues awaiting response for years to be fixed soon or ever... they seem to prioritise UI touches first that guarantee increased sales instead of all those anoying issues in tickets that have been sitting untouched for years.

            Is this going to be fixed?

            Jorden Adams added a comment - Is this going to be fixed?

            Not resolved for me as well. 

            Olga Glukhovskaya added a comment - Not resolved for me as well. 

            Lee Cash added a comment -

            Not fixed. It's been reported as not fixed for years. Wow. How hard is it to review resolved tickets for comments and reopen a ticket? 

            Lee Cash added a comment - Not fixed. It's been reported as not fixed for years. Wow. How hard is it to review resolved tickets for comments and reopen a ticket? 

            This is not resolved. Please reopen. We need the option to restrict epics on a per-project basis. Still an issue in Jira v8.2.1

            brigette riley added a comment - This is not resolved. Please reopen. We need the option to restrict epics on a per-project basis. Still an issue in  Jira v8.2.1

            Same here, I would like to be able to limit Epic selection on a per-project basis only.

            Thomas Mansencal added a comment - Same here, I would like to be able to limit Epic selection on a per-project basis only.

            I completely agree. This is not fixed I just got reported by one of our team members even today again. We are using Jira v8.1.0.

            Shreyansh Hingar added a comment - I completely agree. This is not fixed I just got reported by one of our team members even today again . We are using Jira v8.1.0.

            mgerasolo added a comment -

            I would definitely agree this is not fixed in what I am seeing in 7.6 and 7.13.5.  I work at a Fortune 50 company with a massive Jira deployment.  There are well over 1,000 projects.  The epic link field is essentially unusable.  As an Epic exists structurally/hierarchically within a project, it should not be used across projects (IMO).

             

            Even if you disagree with my opinion, there are clearly enough other people on this ticket and others that share it.  Therefore, I ask that you make it a project level setting to limit epics to just within this project, and then let people choose if they want to select epics from other projects or not.  Additionally the names of some epics are extremely similar.  as each project might have the same epic (Security Auditing, or Complete End Of Year Processes).  I want to make sure the items are linking to the Epic for this particular project only.

            mgerasolo added a comment - I would definitely agree this is not fixed in what I am seeing in 7.6 and 7.13.5.  I work at a Fortune 50 company with a massive Jira deployment.  There are well over 1,000 projects.  The epic link field is essentially unusable.  As an Epic exists structurally/hierarchically within a project, it should not be used across projects (IMO).   Even if you disagree with my opinion, there are clearly enough other people on this ticket and others that share it.  Therefore, I ask that you make it a project level setting to limit epics to just within this project, and then let people choose if they want to select epics from other projects or not.  Additionally the names of some epics are extremely similar.  as each project might have the same epic (Security Auditing, or Complete End Of Year Processes).  I want to make sure the items are linking to the Epic for this particular project only.

             I honestly don't think this is resolved.... nor do all the others trying to figure this out. We may be poor users of Jira, but if that is the case, then educate us or fix this!!!

            James Oliver added a comment -  I honestly don't think this is resolved.... nor do all the others trying to figure this out. We may be poor users of Jira, but if that is the case, then educate us or fix this!!!

            “if an Epic issue type is Invalid,Closed, Done, Resolved” then an issue cannot be added to that Epic

            karthik reddy added a comment - “if an Epic issue type is Invalid,Closed, Done, Resolved” then an issue cannot be added to that Epic

            The issue we have run into is, when folks might not pay close attention, they may select an epic that is closed/invalid  and put a new story/bug in it.

            We’d like to prevent this user behavior if possible. It was proposed we might see if a rule could do that.

            •  Modify the drop down for Epic Link in a Story – can we filter out Closed, Done, Invalid, Resolved Epics from this drop down?
            • Can a rule be implemented that would prevent a Story from linking to an Epic if that Epic is Invalid or Closed?

            karthik reddy added a comment - The issue we have run into is, when folks might not pay close attention, they may select an epic that is closed/invalid  and put a new story/bug in it. We’d like to prevent this user behavior if possible. It was proposed we might see if a rule could do that.  Modify the drop down for Epic Link in a Story – can we filter out Closed, Done, Invalid, Resolved Epics from this drop down? Can a rule be implemented that would  prevent a Story from linking to an Epic if that Epic is Invalid or Closed?

            @marten oh, thanks for info, I had no idea about this. Seems quite counter-intuitive to me. I'll make necessary changes in workflows. 

            Nikola Bornová added a comment - @marten oh, thanks for info, I had no idea about this. Seems quite counter-intuitive to me. I'll make necessary changes in workflows. 

            To implement your recommendation properly, would I need a Epic only Workflow? i.e. what if my Epics and Stories share the same Workflow?

            Karen Rogalski added a comment - To implement your recommendation properly, would I need a Epic only Workflow? i.e. what if my Epics and Stories share the same Workflow?

            @Nikola, @Xavier: The "Show done epics" is not connected to the Status Done, but to the customfield "Epic Status", which has a separate "Done" marker. So for best practice you add a postfunction in your Epic workflow to set the "Epic Status" field to "Done" when you resolve Epics. Unfortunately you need an app for this, e.g. Misc Workflow Extensions.

            Marten Thorand [demicon] added a comment - @Nikola, @Xavier: The "Show done epics" is not connected to the Status Done, but to the customfield "Epic Status", which has a separate "Done" marker. So for best practice you add a postfunction in your Epic workflow to set the "Epic Status" field to "Done" when you resolve Epics. Unfortunately you need an app for this, e.g. Misc Workflow Extensions.

            @Nicola Bornovà : I agree with you. However, I don't know which criteria is used as filter in "Show done epics". It could be "Resolution = Done". But I can't check it, because in either cases (with "Show done epics" checked or unchecked), I have epics in Open status, and Resolution field with "Unresolved". It's a mistery to me.

            Xavier Tang added a comment - @Nicola Bornovà : I agree with you. However, I don't know which criteria is used as filter in "Show done epics". It could be "Resolution = Done". But I can't check it, because in either cases (with "Show done epics" checked or unchecked), I have epics in Open status, and Resolution field with "Unresolved". It's a mistery to me.

            Nikola Bornová added a comment - - edited

            Why is the filter for "Show done epics" connected to status and not to resolution? This doesn't make any sense - we have many Epic workflows with different final status than Done (like Closed, Resolved, Acknowledged etc. etc.). This checkbox should definitely be connected to Resolution, not to Status. (and to be clear - it should be switch between Unresolved or any resolved Resolution)

            Nikola Bornová added a comment - - edited Why is the filter for " Show done epics " connected to status and not to resolution? This doesn't make any sense - we have many Epic workflows with different final status than Done  (like Closed, Resolved, Acknowledged etc. etc.). This checkbox should definitely be connected to Resolution , not to Status. (and to be clear - it should be switch between Unresolved or any resolved Resolution)

            I found in our Jira version,  when I select in Epic link field, Epics of current project are displayed on top of the list in "Suggestions" section. I think that it's rather enough for me. This solution meets the need of who want a limited choices and in the same time that  who wish to have larger choices.

            Xavier Tang added a comment - I found in our Jira version,  when I select in Epic link field, Epics of current project are displayed on top of the list in "Suggestions" section. I think that it's rather enough for me. This solution meets the need of who want a limited choices and in the same time that  who wish to have larger choices.

            Still showing on our cloud version. Can we get a response on this please guys?

            Steve Madden added a comment - Still showing on our cloud version. Can we get a response on this please guys?

            ElodieB added a comment -

            Hi. We still have this issue on Cloud too. Please reopen this request ! 

            ElodieB added a comment - Hi. We still have this issue on Cloud too. Please reopen this request ! 

            Still a huge issue, please fix. 

            Colin Davidson added a comment - Still a huge issue, please fix. 

            NOT FIXED (since 2013 and going.....)

            Still showing ALL the Epics from ALL the Projects !!!!

            Shame on you Atlassian !!!

            It's not a Suggestion it's a BUG !!! a terrible one !!!

             

            Alfredo Vilchis added a comment - NOT FIXED (since 2013 and going.....) Still showing ALL the Epics from ALL the Projects !!!! Shame on you Atlassian !!! It's not a Suggestion it's a BUG !!! a terrible one !!!  

            After commenting above 7 months ago, I just now took another shot at articulating this story as JSWSERVER-16692, which for me too remains unresolved. I dunno, maybe we stand a better chance at getting a "new" issue resolved, than opening a resolved issue.

            Will Rossiter added a comment - After commenting above 7 months ago, I just now took another shot at articulating this story as JSWSERVER-16692 , which for me too remains unresolved. I dunno, maybe we stand a better chance at getting a "new" issue resolved, than opening a resolved issue.

            The same issue. Fix please ASAP.

            Denis Demchik added a comment - The same issue. Fix please ASAP.

            This post and comments began Jan 2014. Hard to believe no one at Atlassian has solutioned this issue.. do you not see the posts or understand how frustrating and non-efficient it is to scroll through a long list of Epics every time stories are created. Jira is supposed to automate and streamline.. make it easy to manage Sprints and stories.. the long Epic list is crazy.. seriously! My company finally gave up and went with a component list instead. Fix the problem! PLEASE!!!

            Michele Varacalli-Shoemake added a comment - This post and comments began Jan 2014. Hard to believe no one at Atlassian has solutioned this issue.. do you not see the posts or understand how frustrating and non-efficient it is to scroll through a long list of Epics every time stories are created. Jira is supposed to automate and streamline.. make it easy to manage Sprints and stories.. the long Epic list is crazy.. seriously! My company finally gave up and went with a component list instead. Fix the problem! PLEASE!!!

            mavilchis added a comment -

            NOT FIXED !!!!!!!!!!!!!!!, still showing ALL the Epics from ALL the Projects !!!!

            mavilchis added a comment - NOT FIXED !!!!!!!!!!!!!!!, still showing ALL the Epics from ALL the Projects !!!!

            Still not fixed. All the epics from all projects are listed in picklist for current project. Frustrating to scroll through a long list every time we create a new user story. Any updates or eta on when this issue will be resolved?

            Michele Varacalli-Shoemake added a comment - Still not fixed. All the epics from all projects are listed in picklist for current project. Frustrating to scroll through a long list every time we create a new user story. Any updates or eta on when this issue will be resolved?

            Is this issue going to be fixed? the ticket status is resolved and the issue is still happening with version 7.2.x

            Stéphanie Garcette added a comment - Is this issue going to be fixed? the ticket status is resolved and the issue is still happening with version 7.2.x

            Why on the Earth is this still an issue? It makes Jira Cloud so unusable and adds security issues. Can it be fixed ASAP?

            Volodymyr Rudyi added a comment - Why on the Earth is this still an issue? It makes Jira Cloud so unusable and adds security issues. Can it be fixed ASAP?

            That is a know issue in Jira Cloud and Atlassian has no resolution for it when I checked about 3 months ago.

            Robert Walch added a comment - That is a know issue in Jira Cloud and Atlassian has no resolution for it when I checked about 3 months ago.

            Epic Links for All projects are still showing up for us as well.  

            Lisa M. Smith added a comment - Epic Links for All projects are still showing up for us as well.  

            Epics Links for all projects are still all showing for me with  Atlassian JIRA Project Management Software v7.3.7.  Please fix this, no need to see Epic links from other projects.

            Greg Nuttall added a comment - Epics Links for all projects are still all showing for me with  Atlassian JIRA Project Management Software v7.3.7.  Please fix this, no need to see Epic links from other projects.

            Not fixed in Jira Cloud either.

            Robert Walch added a comment - Not fixed in Jira Cloud either.

            Peter added a comment -

            Still not fixed for us either (Jira 7.3). For Example when creating a new issue you can link this issue to every epic you are allowed to see overall. Thats not applicable at all! Please fix asap.

            Peter added a comment - Still not fixed for us either (Jira 7.3). For Example when creating a new issue you can link this issue to every epic you are allowed to see overall. Thats not applicable at all! Please fix asap.

            Roger Rolf added a comment - - edited

            Make the epic link smart to only show the epic's from what the board filter is using. so for example if the board filter allow 4 projects, the epic link search should ONLY search across those 4 projects.  If the filter has only one project the search in the epic link will be only across that project.

            This change must happen very soon.

            Btw: I assume that if you don't have permissions to a project in the filter, you wouldn't see this project either.

             

            Roger Rolf added a comment - - edited Make the epic link smart to only show the epic's from what the board filter is using. so for example if the board filter allow 4 projects, the epic link search should ONLY search across those 4 projects.  If the filter has only one project the search in the epic link will be only across that project. This change must happen very soon. Btw: I assume that if you don't have permissions to a project in the filter, you wouldn't see this project either.  

            We are running 7.3.8 version and the issue is still reproducible. Support, please reopen this ticket and fix. Thanks. 

            Sweet Family added a comment - We are running 7.3.8 version and the issue is still reproducible. Support, please reopen this ticket and fix. Thanks. 

            For our company this is a data security issue. Our JIRA instance is used by different clients and its not acceptable that they see epics from projects where they don't have access to. If this issue will not be resolved we unfortunately can't use JIRA anymore.

            Deleted Account (Inactive) added a comment - For our company this is a data security issue. Our JIRA instance is used by different clients and its not acceptable that they see epics from projects where they don't have access to. If this issue will not be resolved we unfortunately can't use JIRA anymore.

            Agreed. This is really confusing, as I'm getting ready to roll out this software to my team. I'm going to have to explain to not cross epics when assigning issues. 

            John Lovell added a comment - Agreed. This is really confusing, as I'm getting ready to roll out this software to my team. I'm going to have to explain to not cross epics when assigning issues. 

            Adding to the pile: the epic link field should show only the project's epics, not global epics.

            Will Rossiter added a comment - Adding to the pile: the epic link field should show only the project's epics, not global epics.

            Michel Ank added a comment -

            I agree too, I didn't see any fix for this.

            Michel Ank added a comment - I agree too, I didn't see any fix for this.

            Agree, this is creating a huge mess for our team. I may not even have the same client on projects and the epics are showing for all projects. Clients are choosing epics from other projects. Should Epics be viewed as global?

            Justin Kuntz added a comment - Agree, this is creating a huge mess for our team. I may not even have the same client on projects and the epics are showing for all projects. Clients are choosing epics from other projects. Should Epics be viewed as global?

            Yea, this still exists 

            Arus Kochinyan added a comment - Yea, this still exists 

            I agree, I don't see this as solved.

            Michael Heumann added a comment - I agree, I don't see this as solved.

            Same problem for me 

            Edgar Ryback added a comment - Same problem for me 

            Ron Chan added a comment -

            This suggestion ticket may be titled "The Epic Link field list Epics from all the projects instead of the current one", but Atlassian did not exactly address that as it was intended. Instead, they added a “Suggestions” section that lists the epics for that particular project. Thus, all epics from other projects (that you have permission to) are still listed below that. Not ideal at all.

            Ron Chan added a comment - This suggestion ticket may be titled " The Epic Link field list Epics from all the projects instead of the current one ", but Atlassian did not exactly address that as it was intended. Instead, they added a “Suggestions” section that lists the epics for that particular project. Thus, all epics from other projects (that you have permission to) are still listed below that. Not ideal at all.

            Hi, has this been resolved?  I'm still seeing all epics from all projects opposed to a single project's assigned epics. 

            Natalie Luisi added a comment - Hi, has this been resolved?  I'm still seeing all epics from all projects opposed to a single project's assigned epics. 

            It would be nice to hide All other epics by default then allow users to click to Show all other epics.
            This would prevent users from accidentally clicking epic names from other projects unless they know exacly what they are doing.

            WEBCODER LTD (EU) added a comment - It would be nice to hide All other epics by default then allow users to click to Show all other epics. This would prevent users from accidentally clicking epic names from other projects unless they know exacly what they are doing.

            Me too.

            Aspa Stathi added a comment - Me too.

            I am also facing the same issue.

            Ayesha Imtiaz added a comment - I am also facing the same issue.

            Ignat (Inactive) added a comment - - edited

            Hi Kim,

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

            Cheers,
            Ignat
            JIRA Bugmaster.

            Ignat (Inactive) added a comment - - edited Hi Kim, If you are still experiencing the issue, please raise a support request at https://support.atlassian.com Cheers, Ignat JIRA Bugmaster.

            Kim Zvik added a comment -

            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?

            Kim Zvik added a comment - 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.

            Adin Poprzanovic added a comment - 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.

            Anestis Kivranoglou added a comment - - edited

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

            Anestis Kivranoglou added a comment - - edited I still see epics from other projects in my Cloud Instance.

            JRob added a comment -

            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)?

            JRob added a comment - 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.

            Martin (Inactive) added a comment - 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.

            Deleted Account (Inactive) added a comment - 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

            Martin (Inactive) added a comment - 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?

            Deleted Account (Inactive) added a comment - 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?

            Martin (Inactive) added a comment - - edited

            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

            Martin (Inactive) added a comment - - edited 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

            Martin (Inactive) added a comment - 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 ?

            Kamlesh Rao added a comment - 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

            Martin (Inactive) added a comment - 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?

            Heather Walden added a comment - 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.

            djackson5280 added a comment - 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

            Martin (Inactive) added a comment - 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 (Inactive) added a comment - 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?

            Ivan Zaguirre added a comment - 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

            Martin (Inactive) added a comment - 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.

            Deleted Account (Inactive) added a comment - 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.

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

                Created:
                Updated:
                Resolved: