Brant Schroeder Community Champion

If it works accept it so others know.

In the JIRA config the Identity provider Entity ID text box should have the SAML Entity ID which you copied from Azure portal this should end in a /. In the Identity provider SSO URL should have the SAML Single Sign-On Service URL which you copied from Azure portal and should not have an ending /. Add the certificate and…

Agents would still have the ability to create a customer or add a customer via raise a request that just prevents external users from creating accounts via email or through the portal.

Place a / on the back of the identity provider entity ID url.

Cloud is more limited. Here is one that I found for cloud: https://marketplace.atlassian.com/plugins/com.stonikbyte.jira.custom.fields.plugin/cloud/overview

This is caused by the incorrect Single Sign-on Issuer configured. Make sure you have copied the entityID attribute correctly, including the trailing slash.

Adrien, One of the core functions of JIRA service desk is to raise requests for individuals that you are working with over phone or email. I don't believe that you can prevent this functionality. There is a request into Atlassian to prevent new creation on CC but nothing to prevent agents from creating customers.

There are several different add-ons that provide this functionality. Here is one example: https://marketplace.atlassian.com/plugins/de.communardo.jira.plugins.userprofile/server/overview

This can be done using issue level security. You can find information on how to do that here: https://confluence.atlassian.com/jirakb/how-to-limit-user-to-only-browse-issues-assigned-to-or-reported-by-them-779160753.html

What groups is the test account associated with?

Can you mark the answer as accepted.

Can you mark the answer as accepted to help others know it works.

Great to hear that can you mark the answer as accepted to help others.

To add application access follow these steps: * Choose > Applications. * Select Application access in the left-hand menu. The Application access page displays all your applications and their associated groups, including their default groups. * Locate the application you want to assign a specific group to, and click…

Jiju, Option One Setup: Groups * jira-user * confluence-user * Internal-User * External-User Users * User 1 - Internal-User, jira-user * User 2 - Internal-User, jira-user * User 3 - External-User, jira-user Projects * Project 1 - For Internal Users Only * Project 2 - For External and Internal Users All default JIRA &…

I think you should just use CSS. You could identify the regions you would like to hide and use display:none property. Center the information and setting a maximum width could also be controlled with CSS.

I would not use SQL Express as your DB. It is also not a supported DB from Atlassian. SQL Express has limitations and functions different then SQL Server. I think that by using a database version that is incompatible with the bundled driver you are having the issue. Do you have a SQL Server DB you could install confluence…

Connor, Since you have verified Confluence has read and write access to its home directory. The next step would be to follow Atlassian's guide to resolve missing attachments in Confluence. https://confluence.atlassian.com/confkb/how-to-resolve-missing-attachments-in-confluence-201761.html

Jiju, Only use confluence-users and jira-software-users to control access to the application, since all users have to have these permissions for licensing, and remove those groups from the default permissions or off of the projects and spaces that they are associated with. Then create additional groups for access to spaces…

In order for the emails to remain in the email account you will need to use IMAP as the protocol. If you use POP they will be deleted. From Atalssian's documentation Emails using POP * The "Deleted" flag set to false, and * Were received after your email account and service desk project were linked. To link your email…

Alex, We just do a nightly snapshot of the VM and the DB. This ended up being the easiest way to backup the system with the least amount of disruption. We have had to recover once and did it without any issue.

In my experience the plugins will time out or fail to load when there are not enough resources available. When I have had issue like this in the past it has to do with processing power. I would start by increasing the time JIRA allows for plugins to load. -Datlassian.plugins.enable.wait=300 you can learn more about that…

The * applied to the Name works since the link name is alphabetically ordered. What you see in the link dropdown will be based on the order of the link name and not alphabetically ordered because it uses the outward and inward descriptions.

Issue links are ordered alphabetically based on the link name. If you have a link type that you would like to place at the top of the list place a * in front of the link name. This will place it at the top making the first or default in the list. The Outward Description and Inward Description can be whatever you would like…

Brain, What you are seeing in the drop down is the transition name. If you open the workflow you will be able to see the transition "Ready for Stage" from one status to the status "Ready for Deployment". All you need to do is edit the transition and update the name to Ready for Deployment. This will fix your issue and then…

You would have to export the report as a PDF. They have to have access to the view access to the project in order to see the issues that you are pulling in the report filter. You can either provide them access to JIRA and the project or make the project public so anyone can see it otherwise the filters will not provide any…

If you do a bulk update that should show in the history. The only issue is that the history will not transfer over in a CSV export so you will loose that portion no matter what you do.

Have you tried applying a different permission schema to the project to see if it becomes visible again to users with the proper permissions?

You could do a bulk update on the server project for that reassigns the reporter and assignee to a user that exists in the cloud. Reexport from server and import into cloud.

A board can have any type of project or issue that is in JIRA. You just need to adjust the Boards filter or when creating the board configuring the filter to include the specific projects and issues. The board will also need to have the proper columns so you can migrate issues to different statuses. Once you have the…