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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

different workflows and screens for different jira teams within one project

Hi, plz help me. I have two or three different teams working in one project . Can I customise workflow or screen for each team?

I want to simplify screen and workflow for one of teams. Maby it is possible to change the screen and workflow depending on an value of "assignee" or value of a custom field within one project ?

Thx at advance.

1 answer

1 accepted

1 vote
Answer accepted

The technical answer is "no".  Screens and workflows are configured by issue type, not users.

This is a good thing - the whole point of an issue tracker is that everyone is seeing and using the same thing in the same way.  While you can work together on something that looks different to each person working on it, it's a right bloody nightmare, and it becomes massively easier if you're all able to see the same information about it.

On the workflow though, you don't need to have everyone use it the same way.   It is still a very bad thing to try to have several workflows for the same item determined by team, but it is absolutely not a bad thing to have one workflow that allows for everyone to do what they need, but limit parts of it by who people are.

Imagine a single workflow of

Open -> Dev -> Test -> Done

Now imagine three roles and the workflows they actually should be using:

  • Developer:  Open -> Dev -> Test
  • Tester: Test -> Done (and Test -> Dev for failed tests)
  • Product owner:  Open -> Done (cancelled), and Done -> Open (I don't think thats what I asked for)

Those are all subsets of the overall process, and Jira workflows can make it look like that  - you put conditions on each transition that limit them to the people who can perform them.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

148 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you