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

Default the project for a new issue to the project of the Epic it is created within

XMLWordPrintable

    • 1
    • 4
    • 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.

      When creating an issue from within an epic the creation screen defaults to the last project whether it matches the epic or not. Customers would like this to default to the parent project of the epic.

            [JSWSERVER-8867] Default the project for a new issue to the project of the Epic it is created within

            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3070462 ] New: JAC Suggestion Workflow 3 [ 3654228 ]

            Benoit Hudson added a comment - - edited

            +1

            We use a project per customer.

            My dev's workflow was: open the Jira board for the project we use for customer B. Open the epics tab. Click create in epic (an epic that only applies to customer B). Oops, it defaults to the project for customer A.

            This causes a risk of leaking information between our customers.

            If you're looking at a particular board it when you click a create link, the project should relate to that board's filter (in my case, that board's filter has project = B).

            Benoit Hudson added a comment - - edited +1 We use a project per customer. My dev's workflow was: open the Jira board for the project we use for customer B. Open the epics tab. Click create in epic (an epic that only applies to customer B). Oops, it defaults to the project for customer A. This causes a risk of leaking information between our customers. If you're looking at a particular board it when you click a create link, the project should relate to that board's filter (in my case, that board's filter has project = B).
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2624515 ] New: JAC Suggestion Workflow [ 3070462 ]
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 3
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 1

              Unassigned Unassigned
              cbenard Carlen Benard (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: