Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

use different due date permissions for different issue types


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
- epic
- task
- subtask

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!


1 answer

1 accepted

2 votes
Answer accepted
Dave Mathijs Community Leader Dec 12, 2022

Hi @Simon Huprich try the following:

  • Create separate workflows for each issue type
  • Add a self-reflecting transition called 'Update Due Date' to each workflow
  • Create separate screen schemes for each issue type
  • Create separate transition screens with the Due date field for each issue type
  • Restrict the transition to a user. group or project role depending on the issue type

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.

Dave Mathijs Community Leader Dec 12, 2022

As you cannot edit permissions "per field" in a permission scheme, you need to add this field to a transition screen and and put a condition on the transition screen itself in order to work. In my opinion, it cannot be achieved otherwise.

Like Simon Huprich likes this
Like Dave Mathijs likes this
Dave Mathijs Community Leader Dec 12, 2022

Thanks to accept the answer if it helped you.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events