Hala ElRoumy Atlassian Team

I really liked the session especially the conversation with SpotOn, it was nice to see real life use cases. Looking forward for the recording. Thanks!

Hi @SAI SAKTHIDAR , Thanks for checking. Can you please contact Rovo Support for further assistance? Thanks!

Hi Don, Thank you for the detailed report of the problem you encountered. Currently, Rovo only supports updating the Summary and Description fields, this is why the Rovo agent/chat couldn't update the Story points. The feature to Create/Edit work items with required/custom fields will be rolled out soon: * Support creating…

Hi Sai, Thank you for your question. Could you please make sure that AI is enabled on your apps? Please check this page for the steps: Activate AI for apps

Welcome, Ciara!!

Great! I'm happy to hear that the problem is fixed! Good luck with your implementation @Sophia Karp !

Hi @Sophia Karp , I'm glad you found it helpful! Can you please make sure that the page ID is correct and the Authorization token is correct?

This is brilliant! Thank you for sharing Ana!

Currently, the resolution field can't be added to the plan timeline. There is a feature request to introduce the ability to add the resolution field to Plans. * Adding a Resolution field to Plans / Advance roadmap I highly encourage you to vote for the feature and watch it to get regular updates on its progress. More…

Hi @Danisse I got it to work by using this JSON in the value: "value": "{{webResponse.body.body.storage.value.substringBefore("</tbody></table>").jsonEncode}}<tr><td>{{issue.key}}</td><td>{{issue.summary}}</td><td>{{issue.assignee.displayName}}</td><td>{{issue.created}}</td></tr></tbody></table>" So basically, I extracted…

Thank you @Chris.Parkes for your feedback! I'm happy that you found it useful! :)

Hi @Kim Serradell, I'm happy to see you found this article helpful. I see Bill has already suggested a good solution. To look further into the rule and help debug it, please contact our support and I would be happy to assist you! Thanks, Hala

Wow this is great! Good luck everyone!

Welcome, Jenn!

Very nice and helpful changes, Thanks for sharing @Irene!

Congratulations All! And a special congrats to my team @Mohanraj Thangamuthu and @Prachi Bolar! Well done guys! 

@Ella Z If there's anything else, let me know ;) 

Hi @Juan D’Achiardi , You are welcome. I'm glad the post was helpful. If you are creating a new page and not updating an existing one, you can just use the Create page endpoint and add the content you want to the page body in the same request. Example: Use the API endpoint Create page with the following configuration: Web…

In this case, can you please open a ticket with our support to further look into this? Atlassian Support: https://support.atlassian.com/contact/#/ Thanks, Hala

Cool! Thanks for sharing @Andras M_ !

Hi Jeremy, It will help a lot to see the actual error message in the audit logs. However, since the field doesn't exist on both issues my assumption would be that the the destination issue (referenced in the branch) where you are trying to set the field is the issue, doesn't have this field. How can you tell which is the…

Thanks, Jeremy. Can you also send a screenshot of the audit log showing an example of a rule execution? Are you getting any errors? Does the CX field exist on both issues? 

Hi John, Usually, this happens when Automation doesn't have access to the Github organization. Can you please check if Atlassian automation is approved under OAuth application policy under GitHub organization settings? User Settings > Applications > Authorise Oauth Applications > Atlassian Automation Link:…

Hi Jeremy, Can you please share the rule that you tried working on to see where the problem is? And maybe a screenshot of the audit log showing the error you encountered if any. Thanks, Hala

Hi Dave, Can you please check if the issue source doesn't have any filters to exclude these missing sprints? Thanks, Hala.

Hi Jordan : ) There are two problems here, let's go though them one by one: * The error encountered updating existing subtasks It's hard to tell what is exactly the problem but judging by the error message Failed to remove subtasks [SDS-136] parents. A parent of a subtask cannot be removed. It seems that there was a…

Hi Mohit : ) Is it possible to add a label to the dummy subtask and have the rule check the label to decide whether to create the Epic or not? Thanks, Hala

Hi Javier, To update existing issues using CSV import, you only need the issue key, Summary, and the fields to be updated. During the import process, please make sure to select the project that the issues are from. For example, if the CSV file has issue key DEV-4 then the you must select the DEV project during the import…

Hi Martin, There are different reasons why issues may not appear in your plan one of which is that they are not included in the plan's issue source. The first step to finding why an issue isn’t showing in your plan is to search for it using the Find your issue function. To find missing issues: * Select Plan settings from…

Hi there : ) In CSV import, Issue IDs are unique random numbers that are only used for mapping issues together (parent/child, issue links ..etc) and you don't need to use the actual issue IDs. If you are going to link new issues during CSV import, you can use random unique number for example: Summary Issue ID Relates Test…