Separate user facing workflow and develop work workflow



We would like to enable our customers visibility of tickets in Jira. We have created a separate project for them, and set the visibility of that user to see only that project. We then bring that issue into our collective board (which has multiple projects into one backlog).


Is it possible for the ticket to have a workflow in our board that is mapped to a different workflow in the customer facing board?


E.g. Our board has several states, "needs refinement, has been refined, work has begin, automated testing, internal testing, UAT, ready for released, released" (Not real, but similar)

We'd like the customer facing board to only have, for example "Reviewed, in progress, uat, released"

needs refinement, has been refined -> Reviewed
work has begin, automated testing, internal testing -> in progress
UAT, ready for release -> uat
released -> released

Is this possible? We'd like not to divulge each step of our process to our customers.


1 answer

0 votes

As you have different projects, yes.  You can have one workflow in the customer project and another in the internal project.  (You can in fact to it by issue type - that's quite common for projects with bugs, improvements and incidents in it - different processes are needed, hence differnt workflows)A board is a view of a selection of issues, and each board can have its own mappings.  I'd keep it simple in your case - a customer board with that simple column-to-customer-status on a 1:1 and then an internal board including both projects, and mapping both sets of status into appropriate column.

Thank you for taking the time to answer - much appreciated.

My understanding of what you have written is that the ticket raised on the customer project will have the status associated with their ticket types and we can drag those around our board columns as the customer ticket status will be mapped to our board. However, those tickets will still only have the reduced state machine of their (customer project) ticket types.

What I'm reading from this is not that you can't map the issue status themselves between projects, but you can map them in your board view to different columns.

This means that tickets being refined before being put in a development sprint will have no mapping, but we can probably work around that somehow.


Thanks again for your time!

That is broadly correct, yes. The status of an issue is determined by the workflow it takes from its project and issue type.  You then use boards to represent these in columns.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,852 views 12 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot