I am in the process of reviewing our current JIRA setup, and I would like to get some feedback.
Currently we have one main product and 3 projects around it:
I read this question, where the suggestion is to use only one project with one workflow that does it all:
Best practice for setting up an 'customer issues' project within an existing Jira installation that is configured around tracking 'internal' issues
I don't want to go that far (yet). However, I have 2 projects, Support and Technical Sales, that are very similar. The only two differences are:
I have two possible solutions regarding the 2 current projects with issues incoming from external sources:
What are the pros and cons of either solution?
Are there any other solutions that I haven't thought about?
Your second solution is not really going to work. Users will be asked which issue types to create, they'll be able to see other stuff in the project that should be internal only, unless you do a lot of config work and use post-functions to set things for them.
The question you've found is a good guide, but ONLY where you don't have the desire to hide things from your customers, and you do.
By far the best solution is for one project per group of people who need to see stuff.
I am sorry but I disagree. If I understand you correctly then we would have to create thousands of projects. Currently our customers can only browse and edit their own issues. They have no access to issues created by other customers. I don't know how the person before me configured it exactly, but it works already. I agree with you on the issue types, but I am looking into JIRA Servicedesk. Once that becomes a mature product, I will be able to create a customer portal where I only offer a limited set of issue types to the customer. I already evaluated JIRA Servicedesk and it does not yet fit our needs because of other reasons, but at least for this aspect it does what we want.
Sorry, you've misunderstood - I mean you should have a project for the internal stuff and another for the external, because you can't restrict users by issue type. Service Desk doesn't actually do the different issue types, it hides JIRA complexity from the customers and makes you map issue types internally.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG