Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-25421

DevOps Automation: When project scope is multiple projects, the Automation does not allow the option *Same project* or *Same project as trigger* when creating a version

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 3
    • 1
    • 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.

      Problem

      When project scope is multiple projects, the Automation does not allow the option Same project or Same project as trigger when creating a version. When selecting the above options under the rule create version in the project, it throws an error as below.

      " Please ensure that project matches your rule's scope as specified in the 'Rule details' section"

      Suggested Solution

      It would be great if the above options work under the project for create a version

      Why This Is Important

      This will help the customer to run the rule only on certain projects and will avoid the need to create multiple rules for each project to create a version

      Workaround

      As of now we need to select all projects to use these options

            [JSWCLOUD-25421] DevOps Automation: When project scope is multiple projects, the Automation does not allow the option *Same project* or *Same project as trigger* when creating a version

            The workaround forces a Global rule to be used. This shouldn't be needed.

            Jason Titley added a comment - The workaround forces a Global rule to be used. This shouldn't be needed.

              eee55d9935eb Andrew Pankevicius (Inactive)
              d31ee7a4b64e Aruna Johny (Inactive)
              Votes:
              11 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: