Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,421
Community Members
 
Community Events
184
Community Groups

WorkFlow Customisation

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.

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 08, 2020

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

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

 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 11, 2020

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.

Comment

Log in or Sign up to comment