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

What is the easiest way to assign users?

Eric Sara

I am in the process of seeing if JIRA is the right tool for our business.

While I know it is targeted at the software development industry I am hoping to extend this.

We are a business that does software development and consulting (this incorporates support and implementations).

I am hoping to find one tool that will work for the whole business so that we have everything together.

I like what I see in JIRA for the development team and even support, however, for implementations I am just not quite there.

I can see that using Agile could be a good answer and I like the way I can see tasks moving through a workflow.

However, I would also like to be able to see who the work is assigned to, what work is unassigned and just move the work to a user. Much like you can move the work through stages.

Has anyone worked with JIRA like this and have any pointers?

Accepted answers

Eric Sara

Just goes to how that reinventing the wheel is not always best.

While the concept above that we were after would work, we have started to use Scrums and are finding that this is working well. I will close this for now in the hope that the direction we are heading will fit our purpose.

All comments

Nic Brough -Adaptavist-

Who is responsible for what work is important in Jira. The core of this is the "assignee" field - Jira works on the assumption that the person named in that field is the person currently working on and owning the issue (and then workload reporting and so-on follows on from that)

You can add more fields to capture more people's interest in the issue. It's not uncommon to see projects that have fields like Developer, QA, Manager and so-on on them, representing ownership inside teams (the assignee remains "the current person in charge of the issue"). For the slightly more advanced users, you often see things like "when issue is moved from development to test, automatically change the assignee to the person named in the QA field".

Then there's estimates, where you estimate how long an issue is going to take. Developers can then log work against issues so you not only get information about work remaing vs done, you can also start to see how good the estimates are (With plugins, you can easily turn that into detailed work reports and timesheets as well)

In short, it's very easy to use the assignee field to drive "who the work is assigned to", "what is unassigned" and rapidly change it.

Eric Sara

I guess what I am looking for is a visual on the assignee filed that could be shown just like the columns in Agile.

Each user, in say a group, would have their own column (with one being unassigned) and the work can be moved from on column to another. It would be good also it if then had a calculation of the total number of hours for that user. I am sure it could be taken even further but I am only looking to keep it simple at this point.

Mizan

Why not set the assignee via a post function ? refer this for setting the assignee .http://plugins.intenso.pl/display/PLUG/Change+Reporter+or+Assignee

Nic Brough -Adaptavist-

That's another good point - you can do quite a lot of automation. Even without complex plugins, you can do things like set an assignee from other fields (If, for example, you set a "QA person" field when the issue is created, you can copy that to assignee when moving into the testing part of the workflow)

Eric Sara

Just goes to how that reinventing the wheel is not always best.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud