-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
2
-
Problem Definition
The Portfolio "Team" field is currently locked. This makes it impossible to make this field required in field configurations.
An important use case is when you have multiple teams using the same project. To be able to separate the different Team's board filters you would want to use the Team field. To make this work you need to make sure field is always filled in to avoid new issues from disappearing from the boards.
When creating an issue and committing this to Jira, you must make a field required in the field configurations. To use a scripted validator will not work in this case, as this will cause an error.
Suggested solution
Unlock field to make it possible to use in field configurations.
- relates to
-
- Gathering Interest
-
- Gathering Interest
- links to
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25255] Add possibilty to make Team field required in field configuration
The solution with adding validator to Team filed upon creation is working, I also use it. However on Edit screen a Team value can be easily removed and I can not control this.
Please, add possibility to make Team filed required.
A work-around i just found is to add a field required validator on the create transition on the workflow. Hope this helps people.
Being able to make such important field mandatory is a must. not a suggestion...
opened for 4 years, another ticket that shouldn't even exist in the first place is about to will be forgotten forever as many others. I'm just shocked how can this platform have so much money and hundreds of forever opened tickets like this.
Agree and support above comments. This field is one of the key reasons we have upgraded to Premium. The lack of ability to make it mandatory is bizarre at best...
This is an important step to make sure that we can rely on this field to be used as the main target group for work to be done. Unless this field cannot made requited to be filled out is like creating a task in an organisation but not making sure (hence forgetting that) someone takes it over.
So unless there isn't the possibility to make that field required we cannot rely on that field which is I why I would ask you to provide that possibility, please. 
This field should be a required field for advanced roadmap users - my department has over 100 users and we've moved to premium account only because we needed Advanced Roadmap feature - could you please resolve this issue?
Using it in a basic JQL search as well as in Quickfilters on a board is key. Somehow I can see the field and its values in basic search - but unfortunately not all which seems strange. When I create a new team in Plans it doesnt show in Jira issue search. However some fields do. Could this be added to that request ?
We really want to switch to Jira Premium full time from our other product management tool, but not having the ability to make the Team a required field AND not being able to use it in Basic Jira search are major gaps.
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC