We are in a next gen software project (kanban). Together with our customer we work on stories. We as developers break them down to tasks. Now we would like to use the estimation feature, yet we want that our customer cannot see anything about estimations. How can we make estimations private to us developers and invisible to the jira user our customer is using?
Thanks for responding to my question. Your answer leads to more questions:
Is there a reason why field-level security is not available for Next Gen projects?
When will it be made available?
Is there an easy way to turn a Next Gen project into a Classic project without changing the look and feel and usage?
Best regards, Martin
There isn't field-level security in either project type - but classic has issue-level security. You can read more about this here.
Using this, you could house estimates in a separate issue type potentially? If you're looking to utilise them in sprints or similar though (eg. story points), there's no easy way to hide these fields I know of in Jira Cloud.
Next-Gen is a newer platform for Jira which is being built from the ground up - I don't know when issue security will be available but you can vote for it in the ideas list - see this issue: JSWCLOUD-18843
You can move Next-Gen issues into a Classic project - but it won't have the Next-Gen functionality, such as the Backlog, at this stage.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure this is possible.
Its unlikely to be possible on either Classic or Next Gen, as field-level security is not a standard feature for Jira - just issue-level and project-level security.
You'll need to consider either a separate Next Gen project for the issues to be estimated - or moving to a Classic Project where you can use issue-level security and place estimations in separate issues you secure.
Ste
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.