Details
-
Suggestion
-
Resolution: Duplicate
-
None
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
- duplicates
-
AUTO-44 Make it easier to work within Automation Service Limits, e.g. increase Daily processing time and Hourly processing time, option to reset/increase limits, show how many components a rule has, option to manage notifications of % service limit reached
- Gathering Interest
- relates to
-
AUTO-730 DevOps Automation: Allow triggers to work with BitBucket Server, Bitbucket Data Center, GitLab On-Premise and GitHub Enterprise, add more smart values and actions for working with pull requests
- Reviewing