Multiple Project Structure

[Evan Giordanella]

I have a single Product Support Service project which intakes Bugs and Product Requests. Part of the workflow of that project is to automatically create tickets/bugs in engineering team's Projects based on component if valid. This is working well. However, there is a part of the organization that does not have Jira access that wants visibility into the backlog of bugs, etc, more than the portal allows. I am curious how best to set this up. I know you can make projects with "Public / Anonymous" access. I am curious how others solve this problem without giving jira licenses or providing too much information. Any suggestions would be great! 

[Sam Nadarajan]

Hello Evan, interesting use case you've got here. I'm not sure as to the specifics but right off the bat I'd say you could:

1. Configure a dashboard with different gadgets and make it publicly viewable. Viewers wouldn't be able to click into a bug to look at the issue details but they'd get some idea into some metrics

2. Put those non-jira users as customers in the project, configure them so that they are all part of 1 organization and have your service project settings to automatically "Share with organization". Those users can go in the portal and see all issues submitted. The problem with this approach is that it would a lot of information with little/no meaning, among other issues.

Best bet would be to find a way to get licenses of course.

Hope this helps

[Evan Giordanella]

What are some other ways, or best practices, for a workflow like this? It is sort of like how you can view public jira tickets within Atlassian support.