Best approach for structure of issues (epics, tasks, subtasks)

[Michal Bergmann]

Hi,
I am new in Jira and setting up it for a small ArchViz team.

Our projects usually have a structure like this:

Which issues and hierarchy should we use? More people work on this project at one time and because just one assignee is necessary to create sub-issues I guess.

Do you recommend using Jira software (JS) or Jira work management (JWM)?
From what I read JS is more used because JWM has some limitations.

I know that Jira is mainly for SW teams however, I like how it works and its great connection to Confluence. So I am searching for how we can use it in a specific field of work.

Thank you for your answers.

[Callum Carlile _Automation Consultants_ · Accepted solution]

Hi @Michal Bergmann , welcome to the Community!

If any of your teams do any kind of development, I'd recommend to use Jira Software, especially if you are using or plan to use agile methodologies, which is what Software is great for as it has Scrum boards with Sprint functionality. Work Management is more aimed at non-software teams and processes such as HR, Finance, basic project management, etc.

JWM has some very simple kanban-style boards (basically just very simple to-do lists), which work well for simple To Do > In Progress > Done type workflows. But generally yes, there's much more you can configure in Jira Software.

It might be worth getting a free trial of each of the tools and having a play around. There's also some good info out there with some good comparisons if you want any more information, such as this one by The Jira Guy (Shoutout to @Rodney Nissen - ReleaseTEAM for the blog!)

Hope this helps :)

[Michal Bergmann]

@Callum Carlile _Automation Consultants_ Thank you for your answer. Do you have idea which issue structure we should use if we decide to go with Jira software? I am not sure if what I drew in original post is good for us.

Thanks also for tip to Rodney Nissen, I've read his article and it's helpful for decision which version of Jira use.

[Callum Carlile _Automation Consultants_]

@Michal Bergmann I think your structure will look very similar to what you have drawn - your 3 clients could all be on the same instance of Jira (unless they require separate instances, or you hadn't planned for them all to be on the same instance?), then you could create 3 separate projects in Jira. You could then create your 5 new issue types (3D modelling, photoshopping etc.) and create a new issue type scheme and add these new issue types to it. You'd then associate this same issue type scheme to your 3 projects.

Depending on your requirements, you then may want to create some separate permission schemes if you only want the clients to see the projects that they are linked to in the above diagram (e.g. projects A and B could share the same permission scheme as all the clients have access to this but you might need to have project C on a different scheme if you only want Client 1 to have access it).

I would also recommend creating your projects as company-managed projects rather than team-managed projects, as you will be able to re-use the issue type and permission schemes

[Michal Bergmann]

@Callum Carlile _Automation Consultants_ Thank you so much for your time.
Do you have an example of the issue type scheme?

We are on the free version up to 10 users currently so maybe this is the feature for a paid version... The same is with the permissions I guess. 

Thanks

[Callum Carlile _Automation Consultants_]

@Michal Bergmann here's an example screenshot:

I found this by going to the Admin Settings > Issues > Issue Type Schemes, then clicked to edit the one associated to my project. Here you can drag and drop your available issue types from the right to the left.

So if you need to create new issue types to add to this scheme, go to Admin Settings > Issues > Issue Types.

Note that this setup is what you would do for company-managed projects, and you don't use these schemes for team-managed projects.

If you're using the free version then you will be able to do the above. You will also be able to create a permission scheme and associate it with a project, but you're unable to add users to specific project roles in project settings - so you would need to use application access/groups when assigning groups of people to permissions in your permission scheme

[Michal Bergmann]

@Callum Carlile _Automation Consultants_ Thank you for your help :-)

[Callum Carlile _Automation Consultants_]

No worries!