We'd like to expand our use of Jira from internal projects to external customer support without pushing up the usercount that much.
It seems as if the anonymous access could handle this, without exposing all issues to public.
So there are some questions left.
Our goal is to have an account for each team member with access to JIRA and confluence, and provide support to several B2B customers, where every customer has several users.
Adding each user to our usercount is not an option as many of those raise one issue a year.
1. Yes, enable the "modify reporter" permission for your internal users, and make sure the field is on the "create" screen. However, you do need to have an account for each user (you could make these dummy accounts - cannot log in, and hence will not use a licence. They'll have to rely on anonymous access to see your issues though). Or you could implement a "customer" select field and hang some reporting off that.
2. No. This is not a flaw in Jira, it's flawed logic. To use a group of objects, you need some way to select how they go in that group. That means you need to know something about the object, and if an object is anonymous, you can't possibly do that. If you don't know who someone is, you can't group them.
3. Confluence has a slightly different access model, but the same basic principles - you can make spaces accessible anonymously.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs