features of JIRA

Good daytime,
we'd like to get a consultation regarding some features of JIRA.

For our professional needs, we require to create several specific accounts in JIRA, which would be able only to create bugs / issues on their own (not see other already created issues),
but their issues should not immediately get into our workflow. At first, they would rather get stored in a certain "preliminary pool", so that a higher JIRA user
could moderate them, in order to verify whether such issue already exists or not, whether it's been created correctly, etc. And then, after such moderation and possible modification,
the issues could be sent into the whole workflow, or terminated by the higher user, with his explaining the reasons to the creator of the issue.

Is it possible in our version of JIRA? If yes, could it be possible for some of your representatives to visit our office and set it up?

Thank you,

4 answers

3 votes

First, this is a community of users, not Atlassian themselves. There are plenty of us who do Jira consultancy, and Atlassian would probably refer you to their partners as well as here.

Anyway, to achieve what you want, I think I would

Enable "reporter browse" permission. When you use that in a project, it enables the reporter to see issues they have raised, but no others in the project (obviously, you'd also include your internal people as users in that project).

Secondly, the moderation stuff is a bit more complex, but I'd recommend simply doing the whole lot in the workflow. When a new issue is created, it can go into "pending moderation", which has two transitions out - one to "not going to fix" and another to "verified, awaiting development". You protect those transitions by having a "role" of "moderator" in the project, adding your moderators to that role, and putting conditions on the transitions that say "moderator only". You could simply educate your developers to ignore issues that are "pending moderation", or you could try to get a bit clever and actively hide them from developers (that may need some plugins and thought - I'd get the rest of it working first)

The bits in quotes there are just names I've taken a guess at, you'll probably have better phrases. Also, this is not the only way to do it, just my initial thoughts on how I would approach it.

of course that is possible...

needs some few settings to be done...

what you're asking for JIRA is covering 100%

no need to visit the office. this can be done remotely

setting up project permission scheme, roles, workflow (including some conditions)

0 vote
Renjith Pillai Community Champion Dec 24, 2012

And to extend what Nic said, if you need a hand in getting things done in JIRA (if you are not able to achieve it by reading the docs), check out the partner list at http://www.atlassian.com/resources/experts/?tab=find-an-expert an contact them. They can help you to get this done.

There are also partners who includes hosting as well.

Many thanks for the help

you're welcome.

feel free to accept the anserwer(s) you find helpful

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,254 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot