Workflows in JIRA are applied to "issue" i.e. each issue goes through some workflow in its life cycle. If we want to add workflow capability for an "entity" in our plugin then can we use same underlying framework to configure and store the workflow related data in JIRA? OR do we need to implement it within our plugin?
Thank you Nic for the reply. If we define issue type for it, then it can be added in a project as a issue, but we are not linking it to project. In our plugin UpRaise, we have performance review form or objectives for which we want to introduce workflow, which is not linked to project but with review cycle and user. Another question - can we use osworkflow in plugin with data stored in plugin related tables. i.e. plugin has its own workflow engine? or will it create any issue with JIRA workflow engine? I need to try it out but if you or someone else has already knows about probable issues, it will save some time. (I accepted answer thinking it will get me some points to add a comment here, but it didn't helped, so tried to upvote both que/answers from my colleague which added 15 points, hope this comment goes through)
As I said already, the workflow engine in JIRA is closely tied to issues. To do workflow on something that is not an issue you have two options 1) Write your own workflow engine 2) Rewrite JIRA so it can use workflow on things that aren't issues - this is not something you can do in an add-on
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot