Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Require commit to be associated with valid Jira issue-is not allowing Maven Release Plugin to commit

Sumanta I'm New Here Aug 05, 2022


I have enabled my repo with a Pre Hook that will ensure that each commit message is associated with valid Jira issue. This setting is working as expected if manually some one is committing.

But this is not allowing Maven Release Plugin to push commits from jenkins, as a result of that, the pipeline is failing with error message

"One or more JIRA issues from your commits not found by query (project = xxxx)"

I am using maven-release-plugin 3.0.0-M4 with mvn release:prepare.

I am using scmCommentPrefix=xxxx-####



If the Pre Hook is disabled, then Maven Release Plugin is able to do commits, and I can see all the commits are actually associated with the specified Jira issue.

Every time i am passing a valid Jira issue in place of xxxx-#### 

Am I doing something wrong here? Please help me.

  • Thanks


0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events