Problem
Issue creation in the context of a user fails with the error "Sorry, you can't create any issues right now, as you need to have access to a JIRA application to be able to create issues"
Solution
| Panel |
|---|
|
From Jira 7 onward, users require application access to at least one application to be able to create issues. Primarily the security context of who is creating issues must be allocated a JIRA seat. The easy case is to automatically join incoming mail JIRA account holders into a group that has application access. If that's not what you want to do, there are two options: - Treat the unprivileged user as an email only user, resorting to storing email addresses of individuals within custom fields. A reporter (eg the User > Default Reporter) will be required to be set to allow this
- Create issues via JEMH Default reporter, in such cases, the security context for issue creation is the default reporter.
For both cases see Create IssuesIssues for clarification of the different approaches to issue creation. |
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@957 |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label = "kb-troubleshooting-article" and type = "page" and space = "KB" |
|---|
| labels | kb-troubleshooting-article |
|---|
|
...