Veera_zqt9p1 Atlassian Team

Just for other community members benefit, posting the answer I have provided to Gil in Support ticket. This is how we can get version name and release date values from Affects Versions system field using smart values. To get the version name, use: {{issue.versions.first.name.asJsonString}} And for version release date:…

Glad to know I was able to help you, Raju. If you don’t have further questions, please accept my answer.

Hi @keevo_tan The Global CSS and JS for Jira addon you are referring to is for Jira Server version, and it's not available for Jira Cloud.

@seethamraju Looks like you have done the integration correct. You will not see the commits in all the issues. You will see the development info only when there is a smart commit linked to it. You may refer below document and test the smart commits.…

You need to be a site admin to access Site Administration page. https://confluence.atlassian.com/cloud/site-and-product-users-938859733.html

Hi @eda_dellaban It's not possible to create project templates in Jira. Do you want to use that template to create new projects? You may use to create projects using shared config as mentioned in the below doc. https://confluence.atlassian.com/jirasoftwarecloud/create-a-project-in-your-new-jira-experience-937886053.html

Hi @Sandeep_Chittybabu As per the screenshot you shared, the user account has been deactivated. Your site-admin will be able to reactivate the account from Administration > Users page.

Hi @ashish.mishra The user may be havimg access other products in your Cloud site, but the access request for Jira still pending. If you are a site-admin, go to your Cloud site Administration > Access requests page and see if the user access request is pending. You need to grant access to the user if it's listed there. You…

@anusha_s26 In Jira Cloud, it's not possible to assign the tissue using user name. You need to use accountId of the user. Please refer the below REST API doc.…

@Zowie Stenroos CNAME is to ensure that Jira is correctly authorised to send mail from your domain using Atlassian's email delivery provider. Yes, you can use TXT records for DKIM, but it'll not authorise Jira to send mail from your domain using Atlassian email provider.

@Hari Sridharala You need to create a screen and add Resolution field to it. Then, attach that screen to _Start Testing_ transition in the workflow so that it'll show a window with Resolution field to the Developer during the transition. Check the below KB article.…

Good to know that it's working now for you, @baraaabbas Let us know if you need any help with Automation for Jira.

Hi @LG Sorry for the late response. Please check the board filter query and see if there is OR clause in it. If that's the case, the board may be trying to pull the tickets from multiple projects. Users need to have _Manage Sprints_ permission across all the projects the filter is trying to pull the tickets from. Below…

Welcome to the community, @StephanieC 

Hi @Hari Sridharala In the new issue view, Resolution field is moved next to the Status field. It'll be visible only when the Resolution value is set. In your example from old issue view, it's showing as Unresolved which is the default value when there is no resolution value is set on the ticket. You may refer to below…

Hi @baraaabbas I just tested from my end it's working fine for me. Is it still not working for you? Are you getting any errors?

@Robert Horan You should be able to do this using the Workflow Validators. You may need to link a screen with the required fields to the workflow transition and validate if the user entered the value for the field using the workflow validator.

You are very welcome, @unnikrishnan 

You are very welcome, @Teri . Glad I was able to help you with it.

@Teri With the current capabilities, it's possible to create 5 standard tasks upon creating an Epic in a Next-gen project. However, it's not possible to link those 5 standard tickets to the Epic. Setting epic link in Next-gen projects is broken in cloud at the moment.

@Teri The Automation for Jira partially works for Next-gen projects. You may refer to the answers provided in the below link. https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Automation-for-Jira-in-Next-Gen/qaq-p/1029987

Hi @unnikrishnan The sections you are referring to in the Backlog are the Sprint names. So, if you want to see the tickets in the correct Sprint section, you may need to change the Sprint field value while changing the status.

Hi @Zowie Stenroos You need to setup the CNAME records as below to ensure that Jira is correctly authorised to send mail from your domain using Atlassian's email delivery provider. s1._domainkey IN CNAME s1._domainkey.atlassian.net.s2._domainkey IN CNAME s2._domainkey.atlassian.net. Make sure that you follow the below…

Hi @Shyju Kammadan You can setup various project level permissions to users/groups/roles. Please refer to Managing project permissions for more details. In your case, you may create 3 different roles/groups for PMO, Managers/Lead and Engineers and grant specific project level permission for each role/group.

Hi @S_K_ You will be able to auto assign the tickets during a transition using a Workflow Post Function.

Congrats @Thomas Schlegel , @Jon Chau, and @Jimmy Seddon

You are very welcome, @Sam Neilson If you are happy with the answer, please accept it.

Hi @Sam Neilson Yes, customers are not charged, and you can add as many customers as you want.

Hi @Sam Neilson There is no limit on the number of customers you can add to a JSD project. The 5000 limit is to sync the user/customer accounts from you Identity Provider (Okta, Azure etc) to you Cloud site.

Hi @Nicole Reichert Welcome to the Atlassian Community!