nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How Atlassian Uses JIRA for Support

pierre.carlier

In this page is describe how Atlassian use Jira for its own support :

https://confluence.atlassian.com/display/Support/How+Atlassian+Uses+JIRA+for+Support

The section about "Issue Security" is not clear : By using a "User Picker" field for "CC users", it allows anybody who can create an issue to access to the whole user database (login, first and last name). Isn't it a "Security Issue" as well ? Is it possible to have similar feature by typing (without autocomplete) user emails ?

How can we autorise a user to share its issue with other users without infringe sensible informations (our customer names) ?

Thanks for your details of how you insure security.

Regards,

Pierre Carlier

Accepted answers

pierre.carlier

We finally decide to create one project for each customer to solve our problem.

We will need to add same versions to each project, but this will be easier than trying to cope with complex rights.

All comments

Timothy

As there is "no" Field Level security in JIRA, either you let them edit the issue (and guess usernames, emails etc.) or you don't let them edit issues.

How can we autorise a user to share its issue with other users without infringe sensible informations (our customer names) ?

Of course, it's up to the editor of the issue to screw up by using a wrong username. Else, you can try this add on (https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.usergrouppicker).

pierre.carlier

Hi, thanks for your answer.

At this time, we didn't find an appropriate solution.

One of our customer have at least 5 accounts on Jira and they want to stay informed for all of their issues. User picking 5 users for each ticket is too long et is error prone.

CC-group would be easier to use but has been removed because of side effects.

As we don't want to create one project for on customer, we don't find other solution than only one account for one customer, which is quite imperfect...

We have Java developper in here. Would it be possible to code a post-create processing to CC-add automatically a group or a list of users ?

Thanks for your attention.

Regards,

Pierre Carlier

pierre.carlier

We finally decide to create one project for each customer to solve our problem.

We will need to add same versions to each project, but this will be easier than trying to cope with complex rights.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

atlassian-support