Details
-
Suggestion
-
Resolution: Low Engagement
-
3
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
There is currently no way to restrict workflow triggers in a project to specific repositories.
Example:
Someone commits a fix with a comment such as "Implementing JIRA-12345 workaround until CORECOMPONENT-123 is fixed"
Both issues would be automatically transitioned to 'In Progress' by this comment, even though no one is actually working on CORECOMPONENT-123.
Suggested Solution
It would be great to allow auto-issue transitions to be configured / restricted by repositories.
This is the customer facing issue for https://jdog.jira-dev.com/browse/FUSE-2786.
Attachments
Issue Links
- is related to
-
JRACLOUD-42577 Automatic workflow transition should only initiate when all pull requests are merged
- Gathering Interest
-
JRASERVER-60101 Allow workflow trigger transitions to happen only for specific repositories
- Gathering Interest
-
FE-4301 Ability to opt a single repository or #pattern out of smart commits
- Not Being Considered