The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Need the ability to restirict developers from moving the ticket status to fixed without a GIT commit. Our current deployment model do not use a CICD pipeline. Therefore, we can't force users to use GIT to deploy the code.
One way we can force users to commit their code to GIT is to prevent their JIRA ticket progression without a GIT commit.
Is this possible in JIRA to check for a GIT commit?
Hi @Family Lee yes this is very possible, providing you have your Jira project connected to a version control system it will track commits and pull requests submitted with a Jira ID in the commit message. JQL for a connected BitBucket Server
fixVersion = x.x.x AND development[pullrequests].open > 0
fixVersion = x.x.x AND development[commits].all > 0
Hi @Family Lee I agree with @Craig Nodwell
Even you can use Automation for Jira to transition issues based on specific git interactions like
New Branch = ToDo -> In Progress
Pull Request Open = In Progress -> Validation
Pull Requect Merged = Validation -> Done
So your team ideally shoudn't move jira issues across the board. Maybe is more about culture problem more than a technical need but with this you could restrinct your team permissions to not move issues across the board
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.