Hi All,
We are using Fix Version for our releases and the same has been associated to issues in Jira. Since Fix Version is a multiselect users are able to select multiple versions for the user stories, to solve this we thought of using Version Picker ( Single Version) but would like to know, will there be any impact on the same.
Any inputs provided will be really helpful as there be data inconsistency if we go through this route.
Thanks,
Vijay
Hi,
I understand that you're using Jira Server and want to prevent your Jira users from entering in more than one value for the fixVersion field on an issue. Certainly, you could use a version select custom field here to only allow for a single version value in that field per issue.
However many of the default reporting options in Jira as well as some gadgets on dashboards are created to focus solely on that fixVersion field. So it might not be an ideal solution to push this proposed change within Jira.
Could you let me know more about your use case here? I am curious as to why you want to restrict the ability of this fixVersion field here. In my experience, many Jira projects might have several versions were a fix can get deployed. Hence the need to have multiple values for that particular field is important to many other use cases.
I imagine that the ability to enter multiple versions here must be causing you some frustration or problem that I am just not seeing yet. Anything more you can tell us about this problem might be helpful for us to better understand your scenario and see if we can offer some advice here.
Regards,
Andy
Hi Andy,
Came across this post when i was looking for answers related to version picker fields limitations.
Is there anyway we can extend release page features to be utilised by version picker type fields too? currently it is limiting some projects in out Jira site. (cloud hosted)
and to answer your question, in our site some projects have multiple teams who want to utilise version fields for their own tracking and it had cause some conflicts and we started using custom field created with version picker type
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.