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
currently I'm configuring a project with special requirements.
So I have a question about the "Due date" field.
The project is using different issue types:
- project initiative
The project lead would like to restrict the possibility to modify the due date:
- project initiative => only project lead should be able to change the due date
- epic => project team members can change the due date
- task => project team members can change the due date
- subtask => project team members can change the due date
- Is it possible to configure different "edit" permissions for different issue types in one project using one set of schemes?
I thought about the following:
1) Permission scheme:
When I assign the schedule issue permission, it is not possible to distinguish between issue types.
2) Field context:
I thought about creating a new context for the field "due date" and assign it to the specific issue type. But unfortunately, I haven't found the possibility to create a field context for the due date field. And I recognized that this functionality doesn't allow to configure the needed behaviour. It just manages options and values, but not permissions of editing.
3) Field configuration:
As I saw, I can assign a specific field configuration to every issue type, but in this configuration I can't modify the permission to edit the field.
What do I miss?
Thank you very much for your help!
Hi @Simon Huprich try the following:
Hi @Dave Mathijs
thank you for your quick response.
According to your suggestion, the only way to fulfil the requirements is modifying screen schemes, workflows, transitions, etc.
But - to understand it correctly - there is no way to configure the same with permissions, field configurations, etc.
Thank you very much.