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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,558,644
Community Members
 
Community Events
184
Community Groups

Use JIRA as workflow engine

I am planning to use JIRA as workflow engine through it REST APIs. In my case, the reporter and the assignee will be defined in different module (not in JIRA). The number of accounts (reporter and assignee) in my application may reach thousands; hence, If I defined them as normal users in JIRA then it will cost me a lot of money and those users will not login or receive any kind of notifications.

How can I create a JIRA task without having the reporter and the assignee defined as normal users. off course, I will create the JIRA using the admin account and then I will change the reporter.

1 comment

Jack [AppFox]
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 14, 2018

Hi Ridwan,

You could use Jira in this way - I would suggest using a single (non-admin) account if this is an integrated application, and then use a field other than Assignee/Reporter to store information on this (e.g. an email or ID) in a text field or store this information separately from Jira.

This will enable you to use a 10-user license for the Workflow engine ($10) and still use Jira as the workflow engine.

I would question whether this is the best approach, as you can use the underlying Java OSWorkflow implementation yourself, or numerous Workflow libraries available for different languages - but I understand Jira may offer an easy-to-use interface.

Jack

Hi Jack

Thanks for your answer. You are right, but that may affect the default workflows, and I will be obliged to define new workflows.

I did not choose a workflow engine yet; I see that JIRA allows customization in both the defined fields and the workflows. And mainly because my workflow is quite simple.

Jack [AppFox]
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 14, 2018

Hi Ridwan,

I don't think you'll have any option but to edit the Workflow that comes with Jira, as you are using it for a purpose other than the one it was intended for.

Given this, there is a graphical drag/drop editor for the Workflow, but you will probably need a plugin like ScriptRunner for Jira or Misc. Workflow Functions to allow you to perform the actions that you want to within Jira.

It sounds to me that just using Jira as a database and then using the REST API to update the items information and workflow state is quite straightforward - it's just a matter of how you create the data without using a different user for each 'reporter'.

I would ignore the 'Reporter' functionality and manage this separately using just a couple of accounts.

If you want to get your hands more dirty, here's a useful page showing some purpose-built solutions:

https://github.com/meirwah/awesome-workflow-engines

Jack

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events