Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-92269

Prioritise parents in the current project when suggesting possible parents for an issue

XMLWordPrintable

    • 3
    • 9

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      The list of possible parents for an issue does not always include the issues from the same project. This is a change in behaviour to the epic link field.

      This only affects company managed projects.

      This is reproducible on Data Center:  No

      Steps to Reproduce

      1. When creating or editing an issue, click into its parent field
      2. Review the list of potential parents suggested by JSW

      Expected Results

      Issues in the same project as the child should be prioritised towards the top of the list.

      Actual Results

      Issues from any project that the current user can view issues for are loaded. Initially they are prioritised by last viewed date, updated date and priority. For subtasks, issues on the BASE level are listed before those on higher levels. For non-subtasks, issues in the same project that were part of the initial grouping are listed first.

      Workaround

      Limiting the 'Browse Projects' permission to a particular project will help.

            [JRACLOUD-92269] Prioritise parents in the current project when suggesting possible parents for an issue

            Amy Petti added a comment -

            This seems more like a bug.   A feature that existed is no longer present with this update.   The option to only show epics within the project is gone, like Federico described in his comment:  https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758/page/6?anon_like=2563752

            Each team at my organization works out of a different Jira project.   The projects are not related to each other, and the people working on them are different.  Seeing epics related to other projects we are not involved with is useless and time consuming to sort through.  

            Amy Petti added a comment - This seems more like a bug.   A feature that existed is no longer present with this update.   The option to only show epics within the project is gone, like Federico described in his comment:  https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758/page/6?anon_like=2563752 Each team at my organization works out of a different Jira project.   The projects are not related to each other, and the people working on them are different.  Seeing epics related to other projects we are not involved with is useless and time consuming to sort through.  

            Shane Buswell added a comment -

            +1 for Prioritise Filter parents in the current project when suggesting possible parents for an issue

            Shane Buswell added a comment - +1 for  Prioritise Filter parents in the current project when suggesting possible parents for an issue

            egaramendi added a comment -

            Hope this ticket will be considered, old epic prioritization was very helpful

            egaramendi added a comment - Hope this ticket will be considered, old epic prioritization was very helpful

            Abhishek Raj added a comment -

            I don't know as to what changed as this feature was available earlier, but we need this feature to be readded to our projects. 

            Abhishek Raj added a comment - I don't know as to what changed as this feature was available earlier, but we need this feature to be readded to our projects. 

            Federico Nardini added a comment - - edited

            I would also like to highlight the fact that, albeit this suggestion is useful, it doesn't solve the missing feature that I described here.

            Federico Nardini added a comment - - edited I would also like to highlight the fact that, albeit this suggestion is useful, it doesn't solve the missing feature that I described here .

            Federico Nardini added a comment -

            +1 to call this a bug, or, if you prefer, a feature regression.

            Using the project-key is a very useful suggestion, albeit it doesn't seem to show the entire list of open epics in project.

            Federico Nardini added a comment - +1 to call this a bug, or, if you prefer, a feature regression. Using the project-key is a very useful suggestion, albeit it doesn't seem to show the entire list of open epics in project.

            Annelotte added a comment - - edited

            Imo this is a bug and not a suggestion or change request, the feature was available with epic links in the past.

            Annelotte added a comment - - edited Imo this is a bug and not a suggestion or change request, the feature was available with epic links in the past.

            Romeo Bollen added a comment - - edited

            This would be a "nice to have", in the meantime we could use the project-key to look for issues in the same project with the search function.

            Romeo Bollen added a comment - - edited This would be a "nice to have", in the meantime we could use the project-key to look for issues in the same project with the search function.

              Unassigned Unassigned
              dshaw2@atlassian.com David Shaw
              Votes:
              36 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated: