nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WorkFlow Customisation

Samuel Olanrewaju

I am hoping to get some help regarding the below;

1. How to enable Workflow dependencies in Fields section.

2. Being able to have only specific fields that can only be managed by assigned people

3. Ability to filter different tickets by fields and responses.

Comments

Nic Brough -Adaptavist-

What do you mean by "workflow dependencies"?

Fields are mostly not limited by user (exceptions are a few of system fields - you can limit due date, assignee and reporter edits to project-roles, groups or other roles). If you want to control access to other fields, you either need an app to limit access, or you need to move the edit of those fields into the workflow and use conditions to limit who can change them.

Yes, you can search for issues by fields and responses

Samuel Olanrewaju

Workflow Dependencies to manage input and output paths. This will ensure some governance in the workflows

Nic Brough -Adaptavist-

Embolding the words does not explain them. "manage input and output paths" is too vague to work with, as is "governance in workflows".

Rather than use buzzword-like phrases, could you explain what you are trying to achieve? Think of it from the end-user point of view maybe? Explain what your Jira users should see and do.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud