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!


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
Community Members
Community Events
Community Groups

SQL query to get properties of workflows


In a few months we would like to migrate to JIRA Cloud. Because some things are not migrated with the MigrationAssistent, therefore i'd like to have an query for the MSSQL DB so i can get a list of the properties and triggers of statuses from each workflow that's existing in our JIRA Server instance.

Is there anyone who can help me? Thank you in advance.

With kind regards, William

2 answers

2 accepted

0 votes
Answer accepted

I suggest you take a look at the Adaptavist server app Microscope. It has a 30 free trial and it’s only $10. This app runs an audit of your workflows and provides a CSV with really useful information about the logic in your workflows and the related app used to create the logic (if applicable).

This tool is now a standard part of our Pre Migration Health Check service we offer as it gives really good information for assessing and planning a migration. 

0 votes
Answer accepted

Select * from jiraworkflow

is the SQL you need.   You'll then have to parse the xml for each workflow.

However, I wouldn't bother.  A raw look at a workflow property doesn't actually tell you a lot without the context in which it is being used.

What you need to be doing is looking at the whole workflow, documenting what it does, and then looking at how you can do what it does on Cloud.  The migration assistant drops some stuff on migration because it's done in a different way in Cloud (or even can't be done)

Rob Horan Community Leader Apr 20, 2022

I have to respectfully disagree.  When you have dozens of workflows with many unique transitions, manually opening each to find opsbar-sequence is not fun.

Like Gita Meskauskas likes this

That's the only way you can edit them too -

A flat list of them, out of the context of their usage is not going to help you with doing anything.

I disagree.  It's a lot easier to export and search on opsbar-sequence than having to go through so many clicks, and waiting for load, and having to go back to the workflow, and then having to scroll back to where you left off.

It would be even easier if the JCMA migrated properties.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events