nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Other workflow types

Charan Kumar

Is ISSUE the only workflow type available or is it possible to create workflows outside of Issues? I am looking to add customized workflows, builds/releases/installations. They are logical workflows, as in, not necessarily scheduled through Jenkins or a CI tool, could be manual copy of files or even configuration changes.

Accepted answers

All comments

Nic Brough -Adaptavist-

I'm sorry, that does not make any sense.

Issue is an issue type. Not a workflow. And, workflows do not have types.

I think what you're looking for is the ability to say "this issue type uses that workflow", which is done with workflow schemes, but your question is so muddled, I cannot be at all sure. Could you explain further?

Charan Kumar

If you don't understand the question ask for n explanation like you did at the end. Do understand that there other tools in the world and nomenclature varies between them. So what makes perfect sense to me, might not for you, which I understand.

Tools like Clearquest and Teamtrack provide ability to create types and individual workflow for each type. In JIRA, I only find the ability to create customized workflows for Issue type. I am wondering, if other types can be created and workflows associated with it.

I also saw references to a build workflow but couldn't find it in the marketplace, can any info be provided on it?

Nic Brough -Adaptavist-

I answered with a set of statements in order to avoid doing it twice - once in the answer and once explaining why your question is nonsense. Sadly, I'm afraid your follow up is the same nonsense and does not help. The references to other tools is irrelevant and pointless, and you've got exactly the same problem with them. Re-read your question and the response and think about what you mean by "type". This isn't a nomenclature issue, it's either some construct you've got in your head which is nonsense, or your use of English is dreadful in explaining what you mean (which is odd because the rest of what you're saying is clear) CQ and Teamtrack do NOT have an ability to "create types and individual workflow for each type", because, as I said, there is no "type". What they do have is the same as Jira - the ability to create issue types. And workflows. And then associate different workflows with different issue types. You repeatedly mention types, and then *separate* issue types from them. What is a "type"? Anyway, a casual glance at Jira would reveal 6 default issue types and 1 workflow. The administration sections have "add" options for both of those, and "workflow schemes" are used to relate workflows to issue types, and that is on a project-by-project basis. You can also generate a number of workflows if you use the project templates.

Nic Brough -Adaptavist-

For the build workflow, yes, you're right, it's not in the marketplace. Part of me wants to suggest it might be tied to the Bamboo plugin, but I'm not sure. There is a page on it at https://confluence.atlassian.com/display/AOD/Integrating+builds+with+your+issues+workflow#Integratingbuildswithyourissuesworkflow-usebuilds too

Norman Abramovitz

I believe you came to the conclusion that you cannot, but only reading through your chit chat, I was wondering if one of these ideas might be useful to you.

If you want to have different workflows for document writers, quality assurance engineers, deployment engineers and software engineers, you could create a subtask issues under the main issue. Each subtask issue could have a different workflow within the same workflow scheme. Each subtask has its own issue type. A subtask cannot have subtasks in the base product. There are plugins that do allow that.

Getting an issue summary across subtasks is a pain without writing a customized code in the above model.

It is not pretty to switch workflows in the middle by changing the issue type, but it is possible. There are way too many questions that need to answered when that is done. I had a single issue where the initial issue type was customer support which was later changed to one of the development issue types. After development was done the manager would switch the issue type back to the customer support issue type. You need to have common entry and exit states/statuses to have a chance for this work reasonably well.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration