Outlook to Jira for restricted Jira projects

I have successfully set up the application in Outlook and it's interface is showing most, but not all of the Projects in my JIRA set up. 

One project in particular (Information Security) is restricted to specific users due to the sensitive nature of the data captured therein. None of the other Outlook to JIRA users can see this project (as expected) however; a valid project user also does not have access to make Jiras in this project. Is there a special permission I have to include to allow Outlook to JIRA to find this missing project?  

Many thanks in advance for any assistance with this matter.

4 answers

1 accepted

1 vote
Accepted answer

As long as the user has the "Browse" and "Create Issue" permission he should see the project in Outlook. There is no special permission which need to be included.

 

Thank you for the response, I will look into this to ensure those permissions are enabled for this user.

Greetings,

So after some review, and project updates, the system works for one of the two restricted issue types. I have reviewed all of the schemes associated and everything seems to line up. I can even see the issue type in the drop down when attempting to create a JIRA from outlook. However; once the "create jira" option is selected, the window opens and nothing populates.

For the second issue type, the window opens and all of the expected fields are there. 

Why would only one of the two issue types work for this particular project? All other projects tested so far do not seem to be affected by this.

 

Thank You for your time and assistance on this matter.

Hello,

After review, the issue was sorted out with the above mentioned problem. 

The associated project was a custom project with custom fields. In one issue type the field "Description" was required and present. In the other issue type that field was not required, therefor not present.

When the Outlook to JIRA attempted to create the issue from Outlook, the screen would appear blank and never resolve because the required filed was not present.

Once I added the Description field to the create tab, the application worked properly. 

It would be a nice enhancement in future releases to return an error screen to alert users of a missing required filed.

 

Thank You for your time and assistance on this matter.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,431 views 0 8
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you