Jira for non-dev projects

[Abdel]

Hey guys,

I've just bought Jira (<10 users).

 I was wondering which type of project is more appropriate for non-software project?

Knowing that I would like to have tasks and multiple levels of sub-tasks as well as taking advantage of SCRUM methodology, board, sprints and daily sprints.

Of course, i've already started to experiment, but I am interrested in the point of views of experimented users?

[Nic Brough -Adaptavist- · Accepted solution]

It depends very much on how you want to handle the non-development process you've got.

You've said you want to take a sprint approach though, which instantly makes me want to say "Use the Scrum Software Development template".  But I suspect you'll probably want to edit the workflow to match your desired process, and then make sure the new flow works for the board.

(Jira only supports one layer of subtasks though)

[Abdel]

Thanks for your reply Nic.
That's right, I like the SCRUM approach with sprints and in the same time define custom workflow, can this be done?

Is it possible to link a business project to a software project to combine the mentioned features?

[Nic Brough -Adaptavist-]

That's what I said, yes.

I'm not sure what you think "combining the mentioned features" will do.

[Abdel]

I mean when creating a custom workflow, how can it be inforced/applied to a project?

Let's say, I edited an existing workflow to add an addition state with transitions and with automatic assignment, how can I apply it to an existing scrum dev project?

[Nic Brough -Adaptavist-]

Most projects (I need to exclude the new "independent" ones created by individuals as they don't have config), have a set of "schemes" that define their behaviour.  These cover things like notifications, permissions, screens to use, field behaviours, and, amongst more, workflows.

To change to a new workflow, or even be a bit more clever and have different ones by issue type (I'm going to use an example with 3 workflows, and many issue types), do this:

• Go into workflows and
  • Create a workflow called wf-Bugs
  • Create a workflow called wf-Changes
  • Create a workflow called wf-stuff-to-do
• Create a new workflow scheme that says:
  • For the issue type Bugs, choose wf-Bugs
  • For the issue type Defects, choose wf-Bugs
  • For the issue type Changes, choose wf-Changes
  • Default (all other issue types): wf-stuff-to-do
• Finally, go to the project admin section and select "change workflow scheme", then select the new scheme you just created.

[Abdel]

Thanks a lot Nic