Status Property

Question

I've added the Status Property <jira.permission.edit.projectrole> which limits the ability to edit as expected.

I am seeing an undesirable affect to my View Issue screen where it only shows a few of the fields it is supposed to. What is causing this and how do I remedy it?

Danno · Answer

@Philipp Sendek _catworkx_ I'm the admin here and up until now I haven't had to start implementing this type of restriction. It had nothing to do with the Hide when Empty feature as you can see in my screen shots. All of the fields were available to the view screen but they weren't being shown if they didn't have a value, unlike the Edit screen where even the empty fields are available.

The clue here for future reference was different tickets that were locked from editing had different fields showing in the view screen. I reopened those two different issues for editing and did a comparison of what was showing in the view and screens and saw that the ones that were available in the view screen had values.

I'm going to try to have default values for all of the fields I want to display when using this property feature, If only Atlassian would allow for locking out editing per field. 😠🙄

Philipp Sendek _catworkx_ · Answer

Hi @Danno ,

that was actually what I was targeting at. Usually, that is the default behaviour, but if you move a field from the "Hide when empty" section to the section above in the Issue Layout, they should display even when empty.
However, I'm not sure whether you're currently in a team managed project and it behaves differently there.

I'm glad you've figured it out! Have a great day!

Greetings
Philipp

Danno · Answer

@Philipp Sendek _catworkx_ STOP THE PRESSES!

Latest news from the front. I was able to get all of the fields to show up in the View issue screen by providing values to all of the fields. I believe this is normal behavior with a View issue screen. If there isn't a value, don't display it. DOH!