CircleCI for Jira

Mainly focused on the orb shortcomings but is fairly limited in feature set and due to not respecting an in progress workflow, will result in premature success or failing to report a failed workflow depending on where you place the jira/notify orb calls. This does apply to larger multi job workflows, as simpler workflows might only have 1 job needed to run completely. Add in another job, and you fall victim to the above issues. To be useful this needs to expand out the workflow statuses and enable a good way to only report on failure until a final step for success of the workflow as a whole. On a side note, it would be nice if this integration was more automatic than manual and reported the status of workflows as it does for github from circleci directly as PR checks. That all being said, it basically forces those that need to integrate circleci and jira to not be able to use the orb but take pieces of it/fork it and create something that actually meets what I would deem as MVP requirements for such an integration.

I write this review as I am having to uninstall and reinstall the app to generate a new token because CircleCI had a security breach. 🤦 I feel like I should be able to manage multiple tokens to avoid downtime instead of reinstalling the app. Frustrated.

The visibility of pipeline builds on tickets, along with the Jira Automation capabilities are super useful. My biggest complains are 1. it doesn't let you query with JQL and it's inconsistent in updating tickets in Jira. Only ~50% of our tickets with PRs that go through CircleCI update with information from CircleCI.