Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-17392 Team-managed software projects
  3. JSWCLOUD-17440

As a Jira Software user, I want to be able to search issues related to Next-Gen projects' epics

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Duplicate
    • Icon: Highest Highest
    • None
    • None
    • None

      For now, the Jira search allows searching issues related to epics only on "classic" projects and the same clauses do not apply to Next-Gen epics.

      It would be very helpful for Next-Gen users to be able to search issues related to Next-Gen epics like "classic projects".

            [JSWCLOUD-17440] As a Jira Software user, I want to be able to search issues related to Next-Gen projects' epics

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 - Restricted [ 3077896 ] New: JAC Sub-task Workflow [ 3475294 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Belto made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Belto made changes -
            Link New: This issue duplicates JSWCLOUD-17239 [ JSWCLOUD-17239 ]

            Belto added a comment - - edited

            Dear Customers,

            After comparing this request against the known report JSWCLOUD-17239 we realised that both are addressing the same scenario. Since we consider JSWCLOUD-17239 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will endeavour to address it.

            Cheers,

            Belto
            Cloud Support Engineer | Amsterdam

            Belto added a comment - - edited Dear Customers, After comparing this request against the known report JSWCLOUD-17239 we realised that both are addressing the same scenario. Since we consider JSWCLOUD-17239 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will endeavour to address it. Cheers, Belto Cloud Support Engineer | Amsterdam

            Alessandro Degano added a comment -

            +1

            Alessandro Degano added a comment - +1
            K. Yamamoto made changes -
            Comment [ A comment with security level 'atlassian-staff' was removed. ]
            K. Yamamoto made changes -
            Link New: This issue relates to JSWCLOUD-17239 [ JSWCLOUD-17239 ]
            K. Yamamoto made changes -
            Link Original: This issue is related to JSWCLOUD-17479 [ JSWCLOUD-17479 ]
            K. Yamamoto made changes -
            Link New: This issue is related to JSWCLOUD-17479 [ JSWCLOUD-17479 ]
            Paula Silveira made changes -
            Component/s Original: Search [ 53297 ]
            Key Original: JRACLOUD-70695 New: JSWCLOUD-17440
            Parent New: JSWCLOUD-17392 [ 1094115 ]
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2868246 ] New: GreenHopper Kanban Workflow 20141014 - Restricted [ 3077896 ]
            Issue Type Original: Suggestion [ 10000 ] New: Sub-task [ 6 ]
            Priority New: Highest [ 1 ]
            Project Original: Jira Cloud (including JIRA Core) [ 18514 ] New: JIRA Software Cloud [ 18511 ]

              Unassigned Unassigned
              htemp Heitor T (Inactive)
              Votes:
              64 Vote for this issue
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: