Project Preferences Status Hide Status | Community
Skip to main content
C
CBuckwal
Level 4
June 5, 2025
Solved

Project Preferences Status Hide Status

  • June 5, 2025
  • 2 replies
  • 581 views

In Project Preferences Status, I used Hide Status in the Queue status set up, thinking that would hide Queue status as an option from non-admin users adding a queue status to their projects. We have request projects set up with queue status and that's the only project type that should have a queue status. I hid queue status in the main system status, but I can still see queue status as an option to add when I log in as a non-admin user project manager. Am I misunderstanding the purpose of hide status or does hide status only work if the status hasn't been used ? Thanks

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by skyehansen

not sure what this means, but if it is successfully hidden, you won't be able to select it unless it was already selected before you hid it. So current projects in Queue status should still show as Queue, and new projects cannot be put into Queue status unless the project's Group field shows a group that has this status visible. So in theory you can hide the Queue status in the system status area, and lock it across all groups. This will hide it overall. Then unlock it. Then go to the one group that needs it to be visible (the Queue group for example) and unhide it for that one group.

 

Summary:

1) make sure you hid the status throughout.

2) the user's "access to the group"(?) has nothing to do with whether they see the status. It's what you put on the Project's group field that populates the status lists in that project.

2 replies

SuryaLakhani
SuryaLakhani
Level 4
June 5, 2025

Double-check if the status was hidden at the system level or the group level. If it is at the system level, make sure it is hidden at the group level too. If done at the group level, make sure the user is assigned to the same home group and the same group is set for the project. 

Ideally, once the status is hidden, it is not visible to the admin in the UI either. You can also just move the Queue status to the very bottom, not hidden, but it works the majority of the time. 

C
CBuckwalAuthor
Level 4
June 5, 2025

Thanks. I had the status hidden at the system and group level and the user had access to the group. It must be since I already used the status that I'm not able to hide it, I guess. Thanks for confirming that the hidden status at the system level won't be accessible to the admin either.

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe ChampionAccepted solution
June 5, 2025

not sure what this means, but if it is successfully hidden, you won't be able to select it unless it was already selected before you hid it. So current projects in Queue status should still show as Queue, and new projects cannot be put into Queue status unless the project's Group field shows a group that has this status visible. So in theory you can hide the Queue status in the system status area, and lock it across all groups. This will hide it overall. Then unlock it. Then go to the one group that needs it to be visible (the Queue group for example) and unhide it for that one group.

 

Summary:

1) make sure you hid the status throughout.

2) the user's "access to the group"(?) has nothing to do with whether they see the status. It's what you put on the Project's group field that populates the status lists in that project.

C
CBuckwalAuthor
Level 4
June 5, 2025

Thanks. I set the queue status up as you described and it works as I hoped it would work.

Terms & ConditionsAccessibility statement

Loading footer...