Error msg : "you must specify a valid version name"

[Nicolas MEHAT]

Hi Support team,

Several of my support teammates complained about the creation of a new version number not being available (as it was before).

They got the error msg "you must specify a valid version name" as attached … I don’t know what to do cause this user seems to have proper permission on “Manage version”, see attached file.

Tks for your help

Nicolas

[Nicolas MEHAT]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Holger Schimanski]

Hello, if you create this version as Project Admin in the Releases Tab, are you able to create that version there? Could you create that version with leaving the release date blank?

[Nicolas MEHAT]

Hello Holger,

As an admin with my account no issue = no error msg;

Unfortunately, with my colleague’s account with a release manager role, the issue persists, see attached file.

Whether the release date field is fulfilled or not the result is still the same, see attached file.

Hope it helps

Nicolas

[Nicolas MEHAT]

‌

[Nicolas MEHAT]

‌

[Nicolas MEHAT]

Permission scheme seems good too :(

‌

[Holger Schimanski]

Thanks for the details. Will look into the code for this.

[Nicolas MEHAT]

Holger,

Additional information/erratum… with my account as an admin project I have the same issue :

Please find hereafter my web browser log files: https://ftp.siradel.com/?ShareToken=B41BFD9C6C4BDA7732F0255F85D409A4A86C94E5

Hope it helps. Nicolas

‌

‌

[Holger Schimanski]

The message You must specify a valid version name (admin.errors.enter.valid.version.name) is provided if an empty version name is submitted, which in your screenshot obviously is not the case, so something strange must be going on.

Which version number of Jira, DC or Server and version number of Version Manager for Jira are you using?

Which web browser are you using? Would Chrome an option for checking the root cause (because in Chrome you have some nice options to track the browser/server interaction with request and response)?

[Nicolas MEHAT]

Holger, Our Jira Server version is 8.20.13 & Jira Service Mgmt 4.20.13 & Version Mgr is 1.3.3.

Previously all reproducing steps were done with Firefox 114.0.2 (64-bit) but now Issue still persists with Chrome 114.0.5735.199 (Official Build) (64-bit) (cohort: Stable)

Hereunder, some HAR logs extracted from Chrome : https://ftp.siradel.com/?ShareToken=517CD8AA968BEEA1739D8368B24309F9869A7F70

Hope it helps.

Regards. Nicolas

‌

[Holger Schimanski]

You are using the right version of Version Manager for Jira for your version of Jira.

I installed Jira Server 8.20.13 with Version Manager for Jira 1.3.3 and Chrome Version 114.0.5735.198 (Offizieller Build) (arm64) on MacOS.

It works for me and I can create versions. So, I have problems to reproduce your issue on my side.

I get the same error message only if I leave the input field for the Version name empty.

It looks like your browser is not submitting the form correctly. In the provided log file I see that the versionmanager webservice is called, but there is no input from the form mentioned. Beside the URL request like http://holgers-macbook.fritz.box:2990/jira/rest/versionmanager/1.0/versionmanager/TEST (my local project is called TEST) the Version and Status should be submitted.

You can see this in Google Chrome using Developer Tools. Please check the Payload of the request.

Under Network please check the Payload of the request. After clicking “Add” button you should see the Version and Status as Payload.

‌

I guess Payload is empty? Could you check and verify?

Maybe you have some browser extension installed blocking certain browser activities?

[Nicolas MEHAT]

Holger,

Thanks for your prompt reply. The issue still persists in a Chrome private navigation with no extra extension loaded. I’ve done a couple of logs and screenshots accessible here :

https://ftp.siradel.com/?ShareToken=485CB5574B776C1C38173DA504BFB7828A130C37

As expected, you are right the payload is empty.

As a reminder, there’s no issue creating a version with the administrative link :

https://ourinternaldomain/plugins/servlet/project-config/SUP/administer-versions

The issue only appears with the sidebar plugin:

https://jira.siradel.com/projects/SUP?selectedItem=jira.plugin.versionmanager:sidebar-item

‌

Please note in the screenshot a difference in the API version called. Don’t know if this is a clue.

Maybe this is also due to some authorizations that are not spread as they should ?

Is there a way to use some Jira tools as re-indexation or others?

Hope it helps.

Nicolas

[Holger Schimanski]

This is the most core feature of Version Manager for Jira and I am really surprised to see this wired issue. There are a hundred installations out there with ten thousands of users and in use since years. I am still thinking what might be going on…

I think it must have something to do with some firewall or security component that is blocking some part of the JavaScript code…

Since when are you using it? Did it work in the past? Is this issue happening for every user of Version Manager for Jira? Or just a couple have issues and other can use it without issues?

[Nicolas MEHAT]

Holger, Thank you so much for your help and reactivity. I don’t know how to explain but now it works. All accounts can now manage versions through the plugin from the sidebar (and not project settings). I am quite surprised to see this working with no action from our side. This is a bit disruptive. Some days ago, I launched a reindex since other manipulation (anonymization). I don’t know if there’s a link between these 2 events. Thank you again for your help. Regards. Nicolas

[Holger Schimanski]

Thank you, Nicolas! This is surprising why it now works, but it is quite a relieve also, because I was very much confused how this could happen. I am closing this ticket now as issue is resolved, but please don‘t hesitate to get in contact again if it is coming again. Or with any other support request 😊