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

Making the team field required


TL;DR - I cannot make the portfolio team field mandatory, even if I unlock it from the DB...

FUll story -

We started using JIRA portfolio, which adds a new "Team" field. previously we had our own custom field for teams.

Since I didn't want to have 2 fields, I bulk updated all of our issues and got rid of the old field to use the new one.... but - our old field was required, and the new field is optional and locked.... I used the following guide so I can unlock it and then make it required:

This went well (more or less) except for the fact that even after I changed the "managed" field set to false, the field still seemed to be locked. I then changed the access level in the DB from "locked" to "Unlocled" and then the field seemed to be unlocked, I then tried to change it to be required, and got an HTTP error. so I am stuck without being able to change it.

Am I doing something wrong? is there another way of doing so or is this a limitation that I somehow have to live with (not sure how)?


2 answers

I just discovered a work-around for this. I added a field required validator on the create transition for the workflow. it doesn't show the field as required on the create screen, but it won't allow the the issue to be created without and gives an appropriate error message if someone tries to create one.

Anyone? Any Idea?

Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Jan 09, 2020

Hi @Ron Grosberg 

Did you get any solution for this, we also face this issue. In-case if you have resolved, please share the solution. Else we might need to contact Atlassian.

Thanks in advance!

Hi @Prakash Palanisamy

Sadly the answer is no. but we actually stopped using portfolio, it did not meat our needs, so it is no longer an issue.

The way we thought to resolve it was paying for the script runner plug-in and then making sure that in the transition of creating an issue this will be a mandatory field.



Like Prakash likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events