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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Can multiple instances use different statuses in their workflows.

Use Case:

Instance One  has determined that their standard Kanban statuses are:

Backlog > Ready for Design > Design in Progress > Selected/Committed > In Progress > Testing in Progress > Done (not linear, btw)

Instance Two has determined that their standard Kanban statuses are:

Backlog > Design > Selected/Committed > In Progress > Testing > Done

Do both instances need to use the same status names? In this use case Instance One is the governing instance and Instance Two will follow their practice. For example:

  • 'Ready for Design', 'Design in Progress' should be used in lieu of 'Design'
  • 'Testing in Progress' should be used for 'Testing'

Thank you!

1 answer

1 accepted

2 votes
Answer accepted
Rich Sparks
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 21, 2020 • edited

Yes, you can do this. You can even vary it by Jira project if you want. However, we don't recommend that because it becomes an administrative burden to keep things in synch.

In Align's configuration for integration with Jira, there's a spot where you can define how Jira states map to Align states (and vice versa.) Align has a specific set of states for each work object (story, feature, capability -- if used --, and epic) and these states can't be changed. That way, there can be a consistent report of the state of work across the enterprise.

You can create what are known as Development Value Streams to support your Instance One and Instance Two scenarios above, and you can then map how each of those custom states maps to Align's standard states.

This article by my colleague @Kent Baxley explains state mapping in even more detail.

Thanks Rich! Appreciate the quick answer. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events