Remove User ability to report

[uday ramakrishna]

I would like to remove the dashbaord option for users or limit them to seeing a dashboard with only open items/issues they have created. As a jira-user they should not have ability to report on other projects and add charts.

[Nic Brough -Adaptavist-]

Why not? If something is so private, they shouldn't report on it, then it's private enough that they shouldn't see it at all. You should simply remove their ability to see it completely. Use permissions to hide the other projects from them.

[uday ramakrishna]

Nic apologies if i am not doing my homework about how Atlassian works. So the "jira-user" should basically be able to create issues, but not create charts and reports. Just be able to view his open cases. Sorry if i am repeating myself. if i remove permissions can they still create new issues?

[Eva]

I had the same question as uday as well. So far I have setup that external users can browse project x, but by browsing permission, it also allow them to create report, which is what I try to avoid. Is there a way we can hide the dashbaorad/reporting via a group check on jsp page?

[Nic Brough -Adaptavist-]

Eva - that's kind of the crux of what I just said to Uday - it's not a case of turning off reporting, all that does is make the users have to work a little harder to find stuff out. There's not much point in doing it - if they're determined to create a report that says bad things, they'll do it.

[Nic Brough -Adaptavist-]

Uday, no, you are looking in the right place. There's two things I'm thinking of here.

First - reporting - there is no good reason to turn this off. If a user wants a bar chart of a load of random issues by project, they can do it with a simple chart. If you remove the ability to do this in Jira, they'll just download it and do it in excel. Also, you can't control it with permissions - all Jira users can create any report that's enabled in Jira.

Secondly, view - this goes back to reporting because Jira will not report on issues that the user cannot see. You can indeed rig up Jira so that a user can raise issues in a project and see only the issues they've raised. In fact, it's better to say "stuff I reported, stuff I'm assigned to and stuff I'm copied in on", but that comes later. This hiding of other people's stuff feeds straight into reports - you can let them do whatever reports they want, but if they can only see 8 issues, their reports will only ever report on those 8.

[uday ramakrishna]

Thanks Nic. The 8 issues limit sounds good. This is not important but just so you are aware why we want to block people from reporting - Users create tickets and typically are the reason they dont get complete on time as against to our promised turnaround times. That said we dont want them to report that we slacked which can be refuted but not worth the effort. Best is to not give the option.

One last question i would have and hope you may the magical answer. On the dashboard i would like to display all cases a particual user has opened and their status in the last 1 month. Is this something possible? I dont want graphs but an easy way they can access their tickets. So a link to their tickets will be good.

[Nic Brough -Adaptavist-]

> That said we dont want them to report that we slacked which can be refuted but not worth the effort. Best is to not give the option.

If they can see the ticket(s), then they have the data they need to claim you slacked off, whether they use a Jira report or not! I think hiding stuff for this case works because if you hide other people's issues from them, they can't say "well you did all of Fred's stuff, why not ours?"

>On the dashboard i would like to display all cases a particual user has opened and their status in the last 1 month. Is this something possible?

Construct a filter for it, save it, and plonk it in the "filter display" gadget. It won't let you show more than a page of 50 at a time, but if you're looking for a month of issues, that shouldn't be a worry. You can customise which columns it displays, so I'd choose at least key, summary and status

[uday ramakrishna]

Thanks Nic i am with you on the comment that we do it for one person but we do not do it for the other. That said i must admit though unfortunate this is the first and only "painful" paid software i have ever used. Using a filter means it is limited to a single project and not across all issues for a given user i am afraid.