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

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.

Hello @Nic Brough _Adaptavist_ , I am encountering the same paradigm, where I have 3 teams within the overall Technology area:

  • IT Operations
  • Software Engineering
  • ERP Specialists

We currently operate using 3 service desk projects, which are displayed in out Customer Portal; however, we would like to compile all support, incident reporting, change management, etc issues under the same JSM project. 

The only I can think of is using workflows  and custom screens as for instance change management screens will vary from an IT request to a new feature on an in house app.

 

Currently each team manages their own related tickets or issues.

Would you be able to recommend a course of action to configure our instance according to our operational flow, and follow best practices?

 

I have been surfing the documentation for a couple of weeks, but can't seem to nail down my understanding in this section of JSM.

 

I appreciate your support.

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

Security Advisory for Jira Service Management

On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link.  We've seen a number of questions already asking for...

258 views 1 2
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