Ajay _view26_ Community Champion

Not an issue with 'Issue Checklist Free'

@Brendan Freestone , We too use Scroll View Port for our Help Documentation. You would need to customize the velocity template based on your styling . Attached is a reference code of our Home page which uses cards. ##========== Search section ================================ <header id="home_header"…

Which checklist App are you using ? We can debug the issue on a trial instance.

@StarVR-Tech The name is copied from the Project Portal Settings.

I see you have checklist App installed . Perhaps that messing something up. Usually the strikethrough works when the Resolution field is set.

Hmm.. should have worked with the post function. Could you check this post which talks about configuration issue

Hmm .. it should be available if the site supports the feature Have a look at https://support.atlassian.com/jira-software-cloud/docs/new-jira-cloud-navigation/#NewJiraCloudnavigation-faq

Kindly try using {{customfield_10308.value}} or {{issue.customfield_10308}} if that doesnt work

Hi @Musa Musayev You can turn the new top navigation from your profile settings

Depends on the use-case you want to achieve when checking for comment is public Refer to the example to use smart values in Automation for Jira

Hi Vivek , Go to your instance to check the execution counts https://{instance}.atlassian.net/plugins/servlet/ac/com.codebarrel.addons.automation/cb-jira-automation-rules#!/ Any time an event fires as a result of an automation rule you have enabled, it will count as a rule execution. Refer documentation for details

Hi @henk aarts Is Ranking a custom field in your Portal page for customers ? You should be able to sort on custom fields in the Agent View.

It seems like the feature is coming up in Next-Gen ServiceDesk projects. However I dont see any option to select a Next-Gen ServiceDesk project on my cloud instance.

Please have a look at the thread which talks of a similar issue. Kindly pos your full catalina.out and atlassian-confluence.log we should be able to help you figure out what is going on.

Hi @KrishnaP Just go to the Issue Activity tab and have a look at the audit trail . You can find the label added date from the activity logs.

@Micah Wilson I would suggest having a look at the free content available in Atlassian University. Kindly refer details here Cheers

Kindly elaborate . Its not clear if you are looking for Workflow configuration for your ServiceDesk Project 

"Automation for Jira" was recently acquired by Atlassian , and is now integrated into the standard edition of Jira/ServiceDesk. This is what you see in the Project Settings under Automation Rules. "Automation for Jira" is way more powerful than the default automation provided in Jira ServiceDesk Project. I believe they…

Perhaps you can read the community article on how to Avoid a cliff-hanger burn-down chart 

Hi @Colin McCririck Can you please check the View configuration . Perhaps the fields you mentioned are set to "Hide when Empty" . You can view this option from the screen configuration/settings option

You can add teams by going to Jira -> People and add your team The names which dont recognise are App user Names. Each App gets a user id allocated on installation for permission management. Hope that clears all your questions. Cheers Ajay

Hi Virginia, You can have a look at customer reporting feature of Apps which can achieve the read only use-case. Ajay

@Virginia Galbarini Customers do have access to view tickets raised by others within their organization. You can have a look at the documentation and configure your servicedesk accordingly Cheers AJ

You can use the issue commented condition 

Hi @Rod , You can add a JQL condition to the Automation rule to achieve the use-case.

As Kian said it would be good add the CEO as a Jira user to achieve the use case. The Marketplace App- Charts & Reports for Jira Service Desk supports sharing feature. Regards AJ

Can you expand on your use-case for configuration. If you need to add additional participants it can be achieved via Jira automation 

Looks like cascading select is not available for next Gen projects

Try out the automation feature which now inbuilt in Jira to achieve the use-case.

Perhaps https://bitly.com/ would be of help ?