Explicit keyword-transition mapping for JIRA plugin auto-close

Jonathan Simon avatarJonathan Simon created an issue

The JIRA plugin currently searches the available transitions for the keyword being used, and executes the first one that contains the keyword.

In some use cases, this is not unambiguous, or users might want to use other keywords in the commit log. This could be solved by making the keyword-transition mapping explicit.

This could be done by just adding the transition ID in the keyword list, such as "resolve/5, resolved/5, start/4" etc. However, there might sometimes be several transitions for the same keyword, depending on the current status of the issue, so maybe "resolve[5,9], resolved[5,9], start[4]" etc.?

Comments (0)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.