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

Do not deprecate Workflow Triggers or allow automation plans to increase automation limits

    XMLWordPrintable

Details

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

    Description

      I hope this is the correct place for this. As discussed here: https://community.atlassian.com/t5/Jira-Software-questions/When-are-the-workflow-triggers-for-branches-going-to-deprecate/qaq-p/1611693 , there is concern in the community around the deprecation of workflow triggers. Many of us are already hitting our automation limits monthly, and without the ability to simply purchase plans to increase automation limits, we're asked to double our Jira subscription costs. 

      While I understand that we can set rules for individual projects, this just isn't feasible when I have 100s of projects on a small team or 1000s for larger teams. One thing changes in that workflow and you're asking us to update 1000 individual rules. 

      Please reconsider the current published solutions and offer better options for your users.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              586f51aa39e0 Andy
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: