You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I want to configure the workflow in such a way that I can hide the display of Story Point for the roles that I select. Tell me how I can solve this issue or give me a link to an article that talks about this
I think this can be manage via Screens and workflow properties
Step 1: Remove the Story Point field from view screen and add it on the Edit Screen only.
Step 2: Make two statuses one for the roles you want that they can view and one for those who can't view and manage the editing rights via workflow properties.
Means that the roles have editing rights can view and edit the story points the other roles can't view and edit. They can only edit on a status where they are allowed.
Hi @Dmitriy Onyshchuk , welcome to the Atlassian Community and thanks for your question!
Please can I ask you for more detail for this use case?
You would like to have a situation where it is possible to enter and store a value for Story Points, but that the value is not visible for some users?
The simplest thing to do would be to have the Story Point field only on the create / edit screens and not on the view screen. This would enable the people who need to manage the Story Points value to be able to use it, but keep the number hidden in the issue. Would that work for your use case?
The point is that I want programmers to be able to estimate tasks before the sprint and in the running sprint so that this is hidden for their roles. But it was shown to other roles
Please tell me what you mean by editing? After clicking which button will you be able to see the number of points?
Hi @Dmitriy Onyshchuk , you can configure, using the screen configuration of the project, to show different fields for different actions as they relate to an issue.
For example, you could, if you wanted, have a create screen that just has the bare minimum of information, let's say, just the summary.
Then, you could have an edit screen, which is what you can see when you click to open an issue after it has been created, which has more fields in it, as maybe the assignee has more information about the work that is required than the creator / reporter.
If you want to be able to edit something but for it not to be shown in the issue view, you can add the field, like Story Points, to only the Edit screen, and remove it from the View. In this way, when you click on the issue to edit it, you will see the Story Points field, otherwise it will not be shown. There are also possibilities as @Muhammad Moazzam Hassan mentions. It depends on you and the project, what you think would be best. If you have a test project or sandbox instance, I would encourage you to try different methods and see which you prefer.