Veera_zqt9p1 Atlassian Team

@Rhonda Urbanczyk You can achieve this by putting the stakeholders into seperate Organisations based on the Site, and share all the relevant tickets with that Organisation. With that all the stakeholders can see tickets created by others in their Organisation. You may refer to below document for more details.…

@Richard Teunen When agent/user click on 'Create an article' in JSD, it'll take them to 'Create page' window where they can choose one of the templates. You can create your own template with the fields so that they can create new articles using that template. Below documents help you understand how to setup templates. Save…

@Timothy Taylor Open the page in edit mode, type / and search for 'Link'. Click on Link macro. Put the URL in the first text field and the text to display in the second one and click enter. You may find more details on Links and Anchors page.

@Martin Zuniga The attachment size setting is mainly for the attachments added by the users/agents in the UI. Jira is not able to process the email messages with large attachments. It's been tracked as a bug in the below link. https://jira.atlassian.com/browse/JSDCLOUD-6172

@Alex Hadden-Boyd You need to remove "Epic Link" field from the screens being used by "Feature" issue type. You can find the screens from Project Settings > Screens page. If the same screen(s) are used by other issue types in your Project and you want to have "Epic Link" field in those issue types, you may need to create…

@LG Changing the ORDER BY clause to "Aha! Rank" field shouldn't cause the issues for you. I have tested it in my test site and working fine for me. Do you mean, 'Create Sprint' button greyed out for you? If the board filter is pulling tickets from multiple projects, make sure you have 'Manage Sprints' permission across all…

Glad to know, @jwood 

@Tom Horton Glad to know you were able to verify your domain and setup the session duration to 1 hour.

You are very welcome, @[deleted] 

Glad to know that you were able to figure it out, @lb852g

Bienvenido a la comunidad de Atlassian, @mosquera-1963 !!!

Welcome to the Atlassian Community, @bete.lopes !!!

@DonPerera Not that I am aware of. JSON web tokens are for authentication your apps. Once authenticated, you will have to use the available REST API endpoints to perform various tasks. So, in this case, the endpoint to edit field configuration is not available at the moment. 

@Pauline Monroy As per the screenshot, the customer account has been deactivated. So, you need to activate the account before you add the customer to a JSD Project. You can reactivate the customer account Jira Administration > Jira Service Desk page where you will see all the customer accounts. If the account was added as…

@Pauline Monroy It seems that you have setup abc.ae as the approved domain in the Site access settings. Yes, when you try to add as the user t@xyz.com from the Administration > Users page, it'll try to create a user account with default product access. However, you can add the customer account directly in the respective…

@Elid Garazlic You need to add 'atlassian-addons-admin' group to Browse users and groups global permission. If you are a Jira admin, you should be able to access Global permissions page using the below link. You will have to change the hostname in the URL to your Cloud hostname.…

Welcome to the Atlassian Community, @Arpita We are glad you are here!

Welcome to the community, @Timothy McCormack 

Hi @Csp3r There could be one of the installation process initiated in the past has been hanging around and it's not letting you initiate another installation. Please reach out to Atlassian Support by providing your Cloud site URL so that they can kill the long running process from the backend which will fix the issue for…

Hi @DonPerera Customer fields scope is defined in the field configuration. Unfortunately, it's not possible at the moment to change the field configuration programatically using REST APIs. There was a feature request raised in the past to Allow configuration of custom field options via REST API, but it was closed due to…

@Gordon Baird In Confluence Cloud New Editor, Code Block macro has been replaced with Code snippet. Code snippet doesn't support customisation. It's been tracked as a feature request: https://jira.atlassian.com/browse/CONFCLOUD-66437

@GME Support The history section may tell you how those comments are marked as internal. Check if there are any 3rd party add-on related automation rules apart from the JSD standard automation rules.

@Thomas Glaser Sorry to hear that your private note has been added as a comment in the Jira ticket. Unfortunately, there is no option in Jira to recall / call back the message sent from a ticket. You may speak to your Project lead or Jira admin who should be able to delete that comment for you. 

You are very welcome @mohithb

@Anuja Deshpande When you subscribe for Confluence Cloud version, you can choose your domain name so that your Cloud site will be created as with that domain name. Let's say if you choose, anuja as your domain, your Cloud site will be created with URL: https://anuja.atlassian.net. Your Cloud URL is the base URL you need to…

@GME Support It seems that those comments are added as internal comments which are not visible on the Customer portal view. Do you have any automation rule setup which might be marking the comment as internal comment?

@mohithb You will be able to do using REST APIs. The Organizations API is available to list all the managed accounts in your Organization. You can use this to enumerate the unique Atlassian account ID for each users. The User management API is available to edit individual users. Use Update a user profile end point to…

@jwood The homepage of the space is restricted. So, you won't be able to view any pages in that space until you get access to homepage. Being the space admin, you can check who has access the homepage from Space Settings > Permissions > Restricted Pages. Then you can ask them to grant you access to it. Alternatively, you…

It'll be easy if you can share screenshots how it looks when you try to edit “Affects Version/s” field from a Story and a Spike.

@coachingthroughcrisis It seems 'Spike' is another issue type similar to 'Story' in your project. Correct? You need to add “Affects Version/s” field to the respective screen used by 'Spike' issue type. You can find the correct screen from Project settings > Screens. Click on the screen used by 'Spike' issue type and…