Restrict Access/Visibility of "original estimation"

Question

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

Nic Brough -Adaptavist- · Answer

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.

Patrick Berger_qdssur · Answer

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- · Answer

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.