The plugin automatically pulls in an issue type like it is a default or something when every new issue is to be created.
image2015-3-6 11:18:33.pngAny suggestions on how to stop this?
So for the Query Issues Custom Fields to work, the admins have to set a specific JQL clause to know what to look for. In my case, I have it look for a specific issue type and that's probably what your administrators have done too as from the looks of it they only want you to be entering Phase tracking issues into that field.
See my example of my Admin screen where I specify an issue type called COTS so when a user types any letter or number into the query issue custom field, it'll only look for issues that match it from issuetype = COTS.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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