You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
It's common for teams to utilize Confluence to plan work, and then use Jira to organize that work. For example, at Comalatech, we have a number of customers who use Confluence to write software requirements, and then use Jira to manage their software development. A simple integration between the ScriptRunner for Confluence and Comala Workflows apps automates this process.
The integration hinges on the script developed by the ScriptRunner team. Running the script in Confluence looks for pages in the "approved" state, which is set by Comala Workflows. The script finds approved pages and then automatically creates Jira issues for each, which teams can then manage in Jira.
Thinking back to the software development example, the process looks like this:
The integration requires both Comala Workflows and ScriptRunner to be installed on the same Confluence instance. You must also clearly identify the “final” states of your Workflow in the script in order for it to work correctly. Here’s the precise steps for configuring the integration:
You can find full instructions for the script, along with a variety of other helpful scripts, in the Adaptavist Library. Likewise, if you want to learn more about everything you can do with Comala Workflows you can head to our website. You can also try both apps for free for 30 days on the Atlassian Marketplace.
Having trouble configuring the script? Feel free to reach out to our support team for assistance.
18 accepted answers