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.
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.
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.
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: