Story point and story point estimate (duplicate?) fields

[Alexander Brockhoff]

Hi all

On my Jira Cloud instance I have two fields, one called Story Points, one called Story points estimate.

The Story points estimate field is reserved in the custom field view so that I cannot delete it, while the Story Points field is not. I took this to assume one was custom created while the other was from Jira.

However, it seems Jira by default is using the Story Points field on the views for my issues and in the reporting for velocity etc. 

Is there something I am doing wrong? What is the proper use of each field? The estimate field doesn't make much sense to me as a field since the Story Points field seems to track changes to itself over time/in a sprint.

[Phill Fox]

Hi @Urmas Kungla

It sounds as though your system has already been amended in a way that is not appropriate for you. So here is a short guide to talk you through how to check your permissions and amend to a more appropriate set.  (There are other configuration options but here we are focussing on those that impact the permission of a person to do a particular action in particular Administrate)

Starting with the global permissions this is what I use (slightly different to the default in that I let everyone manage filters not just those in developer group). <yourhost>/secure/admin/GlobalPermissions!default.jspa

image2016-1-8 8:54:29.png

A key check here is to make sure that JIRA Administrators has not been altered to include the Users or JIRA Users groups.

Next you need to look at each permission scheme in your system.

Here are some of the settings that I use for my default scheme. I change this to remove the reference in most instances to developer and replace with user, but that may not be appropriate to you.

image2016-1-8 8:44:57.png

You need to review all permissions and set according to your requirements and repeat for each permission scheme.

Next is to check the membership of the groups at <yourhost>/admin/groups

In particular check who are members of the Administrator Group.

Then you need to look at the user roles on each project.

<yourhost>/plugins/servlet/project-config/<your project>/roles

and make sure that only users who should have administer permission are listed in the Administrator role, all users who should have access to the project are listed in the User role. You are likely to find that some of this is already covered by the user groups.

If you wish to restrict access to projects to certain users then remove the group users and simply list by name each user that should have access to the project. This can also be managed by anyone with project administration permission.

eg. 
image2016-1-8 9:4:19.png

becomes

image2016-1-8 9:5:42.png

if I want to restrict the project to just myself. 

One final check is to make sure that the settings for application access are correct at <yourhost>/admin/accessconfig

image2016-1-8 8:58:38.png

If Users or JIRA user groups have been added to JIRA administration this will give them the administrator permissions.

Hope this helps you return your system to a more stable situation.

[UrmasK]

Ok, thank you for your time putting together thid guide. I will look into it this weekend and get back to you with the results.

[UrmasK]

I finally got what I wanted- I can change the project and set myself to see everything and new users I can assign to separate projects one by one.

I also understand that I have to remove everyone and every group from every project and then one by one add them again. 

Also, it doesn't matter if I'm an administrator, I have to add myself into the group or user role in the project as well to be able to see it. Just being in administrator group as well gives me more permissions.

At least, when creating a new user, the user can't acces everything.

Thank you, for now, @Phill Fox

[Phill Fox]

Glad to be able to help. If this solved your problem would you mind accepting the answer so that others who search in the future with similar issues have more chance of finding this.

[UrmasK]

The other thing is that when I add a user than after creation the user gets an email with access instructions but I haven't even set up user's groups. It's like I have to work like a superhero in light speed to be able to restrict user access to everything that the user shouldn't see.