How do you handle outside users who may need to see issue details? Best practices?

[Mike Prill]

Hello all, we are a disaster response organization that uses volunteers a LOT to help get things done. We have 200 staff or so, but another 1000 active volunteer leaders who might get called upon to assist with specific tasks/projects from time to time.

I'm curious what the best way is to allow these volunteers to help with specific epics or tasks but not necessarily be able to see all the other sausage making that goes on behind the scenes? 

[Matthias Gaiser _K15t_]

Hi @Mike Prill

some time last year I gave a talk about cross-company collaboration with Jira which mentions several ways how you can collaborate with external people.

In your case, I think an external issue share app would work best. There you can create links for single or a set of issues which you can share with the external users. That sounds to me similar like the Visor app approach, @Michael Yaroshefsky - Visor for Jira suggested.

Hope that helps,
Matthias.

[Michael Yaroshefsky - Visor for Jira]

Hi Mike,

It can be difficult when you have external teams or volunteers who need to see Jira issues. 

• First things first. Make sure everyone is on the same page about the tasks they need to do.
• Next, you can create a separate Jira project for your volunteers, assign specific tasks, and restrict their permissions. (Bear in mind it may get confusing to switch back and forth between projects.)

Alternatively, you can use an app like Visor so your volunteers can work on the issues that are relevant to them and they don't see anything in your company's Jira. You can create a roadmap or timeline for free and Visor syncs to your Jira data, making it easy to make roadmaps that stay accurate: 

https://marketplace.atlassian.com/apps/1226209/visor-flexible-spreadsheet-for-jira-roadmapping-bulk-edits?