Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Transition name is ignored when passed to `jira i <name> --transition`
See original GitHub issueI would expect the following command to transition my issue to “In Progress”
jira i OHANA-1105 --transition "In Progress"
However, it does not… I am just presented with a list of transitions and can select one.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Transition names don't appear when transitioning issues ...
Transition names may or may not display on the issue view status dropdown, depending on the available transitions of the current status.
Read more >Solved: Transition screen to set a resolution ignored when...
The setup is a workflow where on "resolve" transition a screen is in place. This screen has the system field "resolution" on it....
Read more >Configure advanced issue workflows | Atlassian Support
Learn about advanced workflow configuration in Jira Cloud. ... In text mode, select the transition's name from the Transitions (id) column.
Read more >Global transition name didn't display in new issue view - Jira
Currently, the New Issue View displays the names of the transition alongside the names of the statuses where the issue will be set....
Read more >Failure on validator causes Display Name to be replaced by ...
When the original Assignee is "Unassigned" it works fine. It's only if you attempted to Reassign an issue during a transition and forget...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @miguelmich When there would be a new release so we can get this fix from npm?
Hi @miguelmich,
can we get this PR merged, please? It’s a blocker for me to use this package in the context of Github Actions for example.
Thank you