An admin can control who can carry out each and every transition (including based on product roles). Because transitions can be so powerful, they can also be protected. Transitions are special because they let users make this big changes to something - for instance hiding or showing information. How do you change an item's state? The most common way is changing the item's status. When you change an item's state (by changing this bug's status, for instance) you can change how it will look or behave. Workflow let admins control, if you can see something (say a bug), exactly how that bug (for example) should behave based the bug's state at the time. So roles let admins control who can see what in general. One workflow step applies to Bug1 and a different workflow step applies to Bug2. Bug1 and Bug2 look different because their display is controlled by different parts of a workflow system. For example Bug1 may have lots of fields hidden, while Bug2 has every field visible. Users with a role that lets them view incidents can view every single incident in the product.Ī workflow controls what a specific artifact will look like and how it can be edited. These permissions are mostly about what that role can do with each artifact in general. You give users specific roles to give them specific permissions. Permissions and Workflows ¶ How do Spira's permissions and workflows work ¶ What workflow controls a specific artifactĬan I change which workflow step is the default Why does a user not see the right transitions Why can't I change the status of an artifact
Ontime permissions how to#
How to make a field required or hidden or disabled Why is a field disabled or hidden or required
How to stop users being able to delete artifacts How do Spira's permissions and workflows work
0 kommentar(er)
