Fix Version Field - Unable to add new versions

[Jason Corbett]

Hi All,

As an admin, I am able to add new entries to the 'Fixed Version' field within a JIRA ticket.

I have provided admin access to another user within our Product department as they require the ability to be able to do this. However, they are not able to add the version from within the actual issue. They have to add it via the Version list in the backend.

Anyone know if there are any other permissions I need to change to allow this user the ability to add within the issue?

Thanks,

Jason

[Andy Heinzer]

What version of Jira are you using?

In my instance, I had to grant my other user the role of project administrator before they could add new versions to the project.  But once I did this, that account could do so both in the project config page and via the issue itself.  You mentioned they are an admin, but I'm not clear if they are a System admin, a Jira admin, or a project admin here.   Either of the first two roles can give themselves that project admin role, but not all project admins can necessarily give themselves other system permissions.

Does that user see an error message when typing in a new version name?  Curious to see the details of that error.

Does this only happen when editing the issue inline?  Can they create new versions if they click the Edit button on the issue first and then enter a new value to that field there?

[Jason Corbett]

Hi Andrew,

We are using JIRA Service Desk V7.10.

The user is assigned as a jira administrator with full project admin. 

There are no error messages presented. See the below screenshots of what I get (successfully) vs the other user (unsuccessfully)

Hope this helps explain it.

Thanks

Jason

To set some context, there is no V4.6 in the system.

However, when I enter the free text in the field below, it gives me the option of creating a New Version

Fig 1. My admin access allows successful addition

Fig 2. Other users admin access, the system is telling them that there is no match, but is not presenting them with an option to create a new version.

[Andy Heinzer]

Thanks for that info.  I was messing around with this a bit more and I found a way to reproduce the problem here.   In my case, I was able to recreate this issue only when the permission scheme in use by this project removed the

Project Role: Administrators

from the permission called 'Administer Projects'.   In its place I added a just my single user admin account to that specific permission. In this setup, my project user roles still has a role called Administrators, and my 2nd account is a member of that project role. 

When this is setup in this way, I found that my 2nd account could create versions in the project configuration page, but not directly in an issue itself.   It sounds like the same thing could be happening here.   If so, I'd want to take a closer look at your specific permission scheme here and try to understand what groups/roles are specifically given that Administer Projects permission on the permission scheme this project is using.

[Jason Corbett]

The 'Project Role - Administrators' is assigned and this user is a member of the group.

It is really puzzling to be honest.

[Yogesh Mude]

HI @Jason Corbett

That user needs to have a Resolve Issue Permission for that project, check whether he had or not.

[Jason Corbett]

Hi Yogesh,

Thanks for the reply. How can I check that?

Thanks,

Jason

[Yogesh Mude]

Open the Issue/ticket (ex. TST-12) on which he was trying to add the Fix Version and then click on the Admin --> permission helper --> provide the User and in permission (Resolve Issue) and check it.

Please refer the below screen shot for the same.

[Jason Corbett]

Yes, the user has the Resolve Issues permission.

Any other suggestions?

Thanks,

Jason