KyleTryon
commented
1 year ago Hello Friends 👋
The day has finally come 🎉 ! As we have alluded to in a few spots in this repository, we have been working on a new integration for Jira with CircleCI to replace this outdated orb which has historically been difficult for us to update. Today we are excited to announce Jira Integration V2 is finally LIVE!
New Docs: https://circleci.com/docs/jira-plugin/ Orb v2:
- Registry: https://circleci.com/developer/orbs/orb/circleci/jira
- Source: https://github.com/CircleCI-Public/jira-orb
Atlassian Forge App: https://github.com/CircleCI-Public/circleci-for-jira
Key Features
- Open-ID Connect Authentication - No Personal Access Tokens or API keys!
- Fully open source orb with Atlassian Forge backend.
- Optimized orb experience, now much easier to configure.
What to know
- This repo (https://github.com/CircleCI-Public/jira-connect-orb) will be archived shortly.
- We have attempted to address all current issues with this next generation integration. If you experience any issues or have any feature requests please open a new issue in the new repository.
- A video demonstration will be coming out soon.
- We highly recommend moving to v2 of the orb as soon as possible.
Orb version
1.3.1
What happened
Less of an error and more of a request. This orb only allows for a deployment to live in two states: success or failed. Jira itself on the deployments board has may more states and I would like to take advantage of. EG: deployment started, rollback, pending deployment, etc...
Expected behavior
Ideally, it is exposed as a parameter, enum I would guess, that allows a greater degree of flexibility. Do deployments with a blue/green deployment model with rollouts and it would be great to report the status more accurately.