In the Manage Versions administration page, the cog wheel drop down menu for an unreleased version includes the actions "Release" and "Build and Release". In our environment, we are not configured to allow for "Build and Release" to succeed, so it results in a 401 FORBIDDEN error when run by most project administrators.
On the Release tab sheet of the Version summary page, there is only a single Release button and it only executes the "Build and Release" action, which results in the 401 FORBIDDEN error I described earlier. Our project administrators are tripping over this limitation all the time when trying manage versions in their project.
Is there a way to change the behaviour of this Release button through configuration or expose a second button that executes the "Release" action instead of the "Build and Release" action?
Look up for .vm files in your jira install directory. Filenames are pretty descriptive and modifing one of them should do the thing for you.
Be sure to upgrade your jira upgrade procedure in order to copy the file from the old instance to the new one, or at least do the same thing as I described above.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...attest to the experience of an urgent approval that gets lost in the boss’s inbox and requires that special “Please Approve” email or text message. In an age where we have distributed teams...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs