I made some fields mandetrory upon creation on some issues (Parent link for Epics and and Epic link for Stories)
When I create these issues in Portfolio and I add these fields I can't commit the changes as it is still looking for those fields to be populated.
"Epic Link is required"
Am I doing something wrong or is this just not possible?
Well, if I get it right about your problem, as long as your fields are mandatory you have to populate them before commiting the changes.
If you don't want to populate those fields then you have to mark them as optionals.
In portfolio you are already assigning an issue to an epic or feature. So Jira should see that its assigned to a specific epic link in the hierarchy.
The same things will happen if you have portfolio "Teams" as a required field. In the portfolio plan you are already assigning issues to a team. Jira doesn't recognize this and when you commit....you have to assign it to a team AGAIN.
I have to think that this is not intended functionality.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs