Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×After selecting update software runs as normal however when completed page is still showing 2.0.1-j7 installed and 2.0.1b-j7 available for update
Thanks for the information Jim! With some invaluable help from Atlassian (Ben Woskow), the cause of the problem is known and we will fix it soon.
Please note that in this case, as you are using JIRA 7.1.9, it makes no sense to upgrade to version 2.0.1b-J7, that only adds compatibility with JIRA 7.2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jim,
We have reproduced the problem and are working on it. Anyway, it would be great if you can tell us which version of JIRA and UPM are using.
There is a workaround: uninstall version 2.0.1-J7 and then install the latest version 2.0.1b-J7. In the case of Project Configurator this has exactly the same result as upgrading the plugin.
Take into account that the only difference between Project Configurator versions 2.0.1-J7 and 2.0.1b-J7 is that the latter is compatible with JIRA 7.2. In all other aspects they are equivalent.
Best regards!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register Now
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.