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; } } }

Best Project Template to use for non-software related issue tracking with kanban board

Todd Brake

We've had Jira for several years. It was used for a while and fell out of favor due to changes in personnel. Small company, very little IT support.

I'm mechanical engineering manager. We had Jira set up as a simple issue tracker.

Recently, our outsourced software group has begun to use it integrated with bitbucket and teams.

I'm attempting to resurrect it for use in our small mechanical teams, purely as a "change request" system where engineers, field service, or production staff can use a smart phone to report issues and snap photos of issues, that we can use to prioritize and assign the issues, track, and use Kanban board to present progress.

Seems easy enough....

I have two test projects. One is a classic software "kanban" project, and one is a classic business "task tracking" project.

A colleague walked me thru the kanban project, and in general I like it, but would like to eliminate the sort of software specific parts of the issue window. Seems like the business task tracking project will do this.

my first hurdle is I try to create an issue and I get this error "the default assignee does not have assignable permission"

My user is a site admin, but also belongs to groups "administrators, jira-users, site-admins, users" as far as I can tell. What's the deal here?

Any tips on how I can create specific issue types for this business task project? I'm looking for something like the software projects "bug, epic, etc" but maybe with names that will make more sense to the intended audience.

Thanks,

Todd Brake

Accepted answers

All comments

Michael Andolfatto_a62ntx

Hi @Todd Brake , welcome to the Community!

Your first issue would be due to the project's permission scheme- administration groups usually assign the functionality across projects you would expect (when the projects are configured correctly) but each project can still restrict the permission scheme that applies to it.

In this instance, the default assignee does not have the Assignable User permission. You can read more about project permissions here and I would make sure that you read up on the implications of making changes to shared configurations before modifying anything in Jira.

For the issue types, Epics, Stories, etc. are common for Jira Software projects as they are Agile terms. For a Jira Core/Business project with a simple board, it's common to use the Task and Sub-task issue types. You are able to configure custom types as well, but the names will likely depend on what is relevant to your business.

Todd Brake

Michael, thanks much for your reply. I'm poking around in there now, and I understand that at this moment my user can't be the default assignee till I make some changes.... Many of these will be assigned to me, but we won't really have a default user - or, if that's necessary it will be me, and then I'll reassign to other team members.

Let me poke around some and I'll get back to the thread thanks again!

Michael Andolfatto_a62ntx

No problem Todd. The default assignee can be turned off by accessing Project Settings > Details > Default Assignee and setting the value to be Unassigned. You may also be interested in Components, which allow for automatically assigning tickets based on the Component Lead.

Todd Brake

I'm sorta getting somewhere.... but still haven't decided whether to use a software or business type template. Basically fooling around with it.

I found that I had to add myself to the default "user" category to make that problem go away in my Business project. I tried to do what you mentioned, but for some reason I could not change the default assignee value - it was like it was hardcoded. I think I came across a global setting that was set to "NO" something related to this, but I was afraid to change it and screw it up. Adding myself to the user category allowed me to start creating issues.

This was not a problem using a software kanban project.

So I think I figured out how to create different issue types and customize the issue dialog to remove the stuff I don't want. Definitely getting there

Thanks again for your help!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud