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

Create Version Component error - Please ensure that project matches your rule's scope as specified in the 'Rule details' section

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 10
    • 8

    • 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

      The Create Version Automation rule throws the following error when scoped to Multiple Projects:

       

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

      Suggested Solution

      Allow the Create Version component with the Multiple projects scope

      (Add a suggested solution once one has been determined)

      Why This Is Important

      (Add a description for why this is important)
      I need to be able to create versions ina few, not all projects

      Workaround

      (Add a workaround, if available)

        1. Screenshot 2023-02-22 at 19.13.31.png
          Screenshot 2023-02-22 at 19.13.31.png
          72 kB
        2. Screenshot 2023-02-22 at 19.13.42.png
          Screenshot 2023-02-22 at 19.13.42.png
          51 kB

            [JSWCLOUD-24213] Create Version Component error - Please ensure that project matches your rule's scope as specified in the 'Rule details' section

            George Gaynor added a comment -

            I also have this issue but now it wont let me save changes to it. very frustrating. 

            George Gaynor added a comment - I also have this issue but now it wont let me save changes to it. very frustrating. 

            Pijus Juodis added a comment -

            For me it strangely allowed saving the actual rule even with this error message.

            Once the rule was saved, it did determine the project correctly and created the version properly. The component still shows a warning whenever I'm editing the rule, but essentially it works.

            I chose Same project as trigger, but I assume it would work with Same project as well.

            Pijus Juodis added a comment - For me it strangely allowed saving the actual rule even with this error message. Once the rule was saved, it did determine the project correctly and created the version properly. The component still shows a warning whenever I'm editing the rule, but essentially it works. I chose Same project as trigger, but I assume it would work with Same project as well.

              eee55d9935eb Andrew Pankevicius (Inactive)
              419e4a896960 Phumi
              Votes:
              37 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: