Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Restrict Access/Visibility of "original estimation"

Patrick Berger
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 6, 2023

Hi all

 

In several projects we work with external partners (mostly this are developers). The Projectmanagement and issue-creation is covered by internal members.

So our current workflow is, that we create epics, assign issues (user stories) an make a first time estimation for each issue (used for roadmapp planing and dealing with ressources). then the issues are assigned to an external developer, who in turn estimates (remaing work) and logs the effort via Tempo.

Now we don't want that the external members can see our original estimation. In case our first estimation was to high, someone could let us pay our original estimation but had a lot less work to do.

 

Is it possible to restrict the visibility of specific fields just to certain roles?

 

Best regards,

Patrick

2 answers

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 6, 2023

Welcome to the Atlassian Community!

Jira does not have any security below the issue level, you can't hide fields from people.

On Server/DC, Tempo did actually enable you to hide worklogs, if you set it to be the primary time-tracking system.  I don't know if it is the same on Cloud, but it may be worth a look.

1 vote
Ojase Emmanuval
Community Champion
July 6, 2023

@Patrick Berger Welcome to the community !!

You may have to use a market plugin like scriptrunner to achieve this.

https://docs.adaptavist.com/sr4jc/latest/features/behaviours

Thanks,

Ojase

Patrick Berger
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 7, 2023

Hi

Thanks for the recommendation.

Actually Behaviours doesn't support "Original Estimation" (this is a system field). 

 

After some research I found this:

https://community.atlassian.com/t5/Jira-Software-questions/JIRA-Restricting-the-original-estimate-field-once-it-is-set-by-a/qaq-p/586270

https://jira.atlassian.com/browse/JRASERVER-1330

 

It seems that JIRA doesn't support such a basic feature.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 7, 2023

It's not a "basic feature", it's a "not useful feature" in a system that is intended for collaboration - the idea is that everyone should be working with the same information, not have bits of it missing.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events