Marc -Devoteam- Community Champion

Hi @Jan Rosar This would be correct. What is the detail of the trigger of the automation, is this based on value deletion? If so, try the following. Set the branch to advanced branching and the branch details to: {{triggerIssue.parent}}, name the variable, then do the lookup en and the edit on story points, does this give…

Hi @Fatoumata Siga Coulibaly Is the organization linked to the project? See this KB article on how to link an organization to a project. https://support.atlassian.com/jira-service-management-cloud/docs/add-an-organization-to-a-service-project/

Hi @Sonia Mathew It could be that the cipher suite used is to old, see the following article on the most updated TLS cipher suites supported https://support.atlassian.com/security-and-access-policies/docs/supported-security-protocols-for-atlassian-cloud-products/ 

Hi @Antoine de Wasseige Welcome to the community. As stated on enabling the feature; "Use suggestions to help your team gather context quickly and act on suggested actions. Powered by Atlassian Intelligence, this feature is available for service requests and incidents only" So no this can't be on other issue types then…

Hi @Alex Davidovic Welcome to the community. Please reach out to the support of the Clockify app, as this seems to be triggerd from their end. Community members are here to help other people with issue or question around Atlassian products, but we can't fix: * User access * Billing * 3rd party app issues * ...

Hi @Priyanka Agrawal You can use the API, see api-rest-api-3-issuelink-linkid-delete Still this will have a limit as well, its not specified.

Hi @Vishal vanpariya Welcome to the community. There is no endpoint on the xray api to update existing tests steps only to import them. this can only be achieved by using Importing+Tests+using+Test+Case+Importer here in the CSV you can specify the existing issue key

Hi @Jan Rosar As I mentioned, in the text, change the trigger to look at the field parent. Then the automation looks if the parent field is changed, it will continue if the issue is not and Epic, then it will update the Story Points on the Epic. Adjust the lookup query to "Parent" = {{issue.key}}

Hi @Jan Rosar Welcome to the community. See the following automation rule, of a simple story point sum up in the Epic. In the lookup action change this to "Parent" = {{issue.key}} You could change the trigger to value change for parent, or use both fields.

Hi @Leslie Silva using the field requires you to drag it to the form, to remove it, use the option "Manage your from fields"

Hi @Deepak Rai Then this endpoint has been removed, I knew it was related to the old rest API version. So unfortunate this can't be used anymore. So there are no rest api options anymore and so currently no workarounds.

Hi @MEA Welcome to the community. Are request type in the project set to be visible on the portal or are they set as hidden? There need to be visible request types, otherwise the portal will be empty

You could also have your jira user act as contributors on the raised requests, this wiil prevent creating duplicate issues in the system. See the roles in JSM, what-users-and-roles-are-there-in-jira-service-management Contributors can add comments to the issues, but no transition the issues.

Hi @Avigail Max What do you exactly see a the solution here? Why create duplicate issues, you solution teams should be working in the JSM project. Issue raised on JSM can't be in a normal Jira project, then you would need to use automation to create a linked issue in the teams project, is this your view and/or wow?

So this Actions is a field. You can't use form information like this. You can't compare this in this way, the information stored in the form options are not variables. You could try if you could store the form field output in a variable and then use this to compare

Hi @Ramprasad Welcome to the community. Opsgenie/Alerting is based on Incident Management not Major incident in specific. But on Free tier you can't use this. "As of October 16, 2024, advanced incident management capabilities (such as major incidents and post-incident reviews) for Jira Service Management will move from…

Hi @Leslie Silva Welcome to the community. Can you show a screenshot of the form, pleasse.

Hi @Jack Black There was a webinar on this today. It will start rolling on Free tier, then standard and then premium. There will be announcements made on when the new UI will be rolling out

Hi @Erik van der Valk What is your goal with your automation, log the values selected? The set values can be seen in the form linked to the issue. As I understand, you want to use information from the form to trigger an automation rule to create an issue in another project. So this is not when the form is submitted, but at…

Hi @Kira Anderson _ADMIN_ As mentioned in the linked article above, then new issues view (default view now) doesn't adhere to this property setting anymore

Hi @Steeve P_ What are you trying to accomplish, an automated transition done by an automation rule. But there is a mandatory comment required on the transition. Is my understanding correct?

Hi @Simona Guedez La Torre This is currently not an option. You can vote and watch the following feature request, JRACLOUD-16281 

Hi @Rangga Hardono Can you try another browser or incognito window, if this doesn't work, contact Atlassian Support I check multiple project on my instance and I can view the widget.

Hi @Vinícius Pereira In the board configuration, what field is used for Estimation, setting Estimativa. In my mind it relates to that.

Hi @Kira Anderson _ADMIN_ So what have you set as property values for the different transitions, but since the new issue view, this seems not to work anymore See How-to-reorder-status-transitions-in-the-new-issue-view 

Hi @Greg Zielinski If you specify the issue in slack to the use with the 3 dots option, they should have the option to transition the issue, but I don't know if this can be done if a user is not an agent. You cold also opt for an automation rule that based on issues in a certain status will sent out a slack message to the…

Hi @Vinícius Pereira On the project view the relevant board and configure the board and choose the Card Layout option to specify the fields on the card. Remove the fields you don't need and add the fields you need. What field is used for estimation in the board settings?

Hi @Amir Atadjanov Contact the developer/vendor in this case. I see this is "Free App", free apps have a riks that the developer is not updating this, based on changes in the Cloud SaaS Atlassian product. I think, this is the app right?…

Hi @Bryan (Oud) Welcome to the community. Is the behaviour the same in another browser or incognito window? If it does, then this seems an instance related issue and raise your issue with Atlassian Support

Hi @Adam Bang You described the option available. If you want this otherwise, you will need to purchase an JQL extensions app from the marketplace. Natively there is an automation option for this. "Adds specific label to Epics with no children. The trigger can we scheduled to run once a day, or just when someone creates an…