Gaurav_0av1h6 Expert

Hello @Rohan Mahy Welcome to the community!! For the mentioned use case, I have created an Automation and it works as expected. Please find below the screenshot of the parent and child ticket, which have been updated based on my understanding of the use case. Following them are the screenshots of the Automation rule. The…

Hello @Julian Reichle In my understanding, this is the Child Page macro. This can be set up to display the child pages of a given parent page. Kindly accept the answer if this helps resolve the query.

Hello @praktikant3 Please try the following: 1. For the JQL filter, use the condition as "project = "ITSM project" AND (due<=now() AND duedate >= startOfMonth(-12M))". This can be further customised to include the condition for Status as well. project = "ITSM project" AND (due<=now() AND duedate >= startOfMonth(-12M)) AND…

Hello @vyomkesh saxena Welcome to the community!! For this use case, please follow the following steps: * Navigate to the board * Click on the 3 Dots available on the top right-hand side * Click on Board Settings * Go to Swimlanes * Set it up as shown in the screenshot, customizing as per the required containers Please…

Hello @Alex Phipps Could you please confirm if you are using any plugin for the team planner? From the screenshot, it seems like some has manually created this for your team. If this is the case, then you will have to extend this manually for the next year and similarly every year. If you are not aware, please check with…

Hello @Michael Woong For this scenario, you can create a filter and use the condition 'timespent >= 2h'. This can be customised as per your use case to include the relevant project, issue types etc. Also, if you need an email alert for such cases, Automation can be leveraged. Kindly accept the answer if this helps resolve…

Hello @BrentBot This can be accomplished by using Automation. The trigger can be set as Issue Transition to the required state, validated for issue type, and then the content can be copied. Please let me know if you need help with the exact rule level details.

Hello @kotha Eswar rao As this is a smart value, I have not used it in JQLs but in Automation. I would suggest you please try it as ('{{comment.internal}}' is 'false').

Hello @kotha Eswar rao For identifying the external comment, there is a smart value available. Checking if the smart value '{{comment.internal}}' is false would help identify the external comments.

@NY I think the query is missing some sections as 'component = "project" = Backlog' does not make sense. Based on my understanding and limited view, I would suggest the following: component = "project" AND status in (Backlog, InProgress, "To Do", Test, Done)

@NY You can define the number of results you wish to visualize while configuring the gadget. I am not aware of the maximum limit for the count of results the gadget supports. Kindly accept the answer if this helps you.

@Albert Manuel Even I have used the same property as mentioned by you. And the rule trigger which I (Issue Commented) used is available on the server as well. I would suggest you test it in your environment and share the findings.

@BrentBot In this case, we need to have a connection between which Discovery issue should update which Presentation Design ticket. If that is not done, then when any one of the Discovery tickets is moved to the Approved status, then all of the Presentation Design tickets would be updated. I do not think that is the…

@BrentBot Please confirm the following: * Can a single Epic have more than 1 issue which is of issue type 'Discovery'? * Can a single Epic have more than 1 issue which is of issue type 'Presentation Design'?

Just to understand the use case better, can there be multiple issues of type 'Discovery' and 'Penetration Design' within an Epic? In case there can be more than 1 issue of any of these types, then the general rule would copy from each issue of 'Discovery' type when it transitions and copy to each issue of 'Penetration…

Hello @NY Assuming that the 5 attributes being referred to are Status. When you configure the gadget, it asks for the parameter to be shown on X-Axis and Y-Axis. Based on your use case, you can select from multiple options available. Let me know if this helps.

Hello @Albert Manuel To mimic your scenario, I have implemented the restriction on comments for closed tickets. Post this, reply to that mail thread for the closed ticket created a new ticket and informed about the new ticket as well. The comment was captured as the description of the new ticket. Please refer to the below…

Hello @BrentBot The system can look for specific issues under the epic but we need to define a condition that will help execute this across different epics.

Hello @Kristin Beck Please create a copy of the exported file, unzip it, open the entities.xml file and look for ZLIB. Also, please scan the logs on the server for the error message details. It will provide you with more insights into the root cause. I would suggest opening a case with Atlassian as well for this issue.

@NY Please refer to the below screenshot which shows 2 different gadgets for showing the issue counts. Filter Statistics uses a filter query that can be customized as per your use case. Filter Counts refers to a project and the required status can be selected. .

@NY Kindly clarify what you are referring to by Filter Script.

For the counts, you can make use of the 'filter statistics' gadget. Navigate to your dashboard --> Add a gadget --> Select "filter statistics" --> Save In the configuration, choose to display the saved filter, and "Status" as the "statistic" you want to report on. Save the config, go to the dashboard; to visualize the…

Hello @[deleted] In order to do this, you will need the system administrator privileges.

Hello @Kristin Beck As you informed that the import does not work properly, can you please share the error message which shows up on the screen. Also, I would suggest checking the logs for the confluence server which will have the details of the error. If you share the error message, this would help us suggest appropriate…

Hello @[deleted] This scenario can be approached in the following manner: * When an issue is created * If the issue type is 'BUG' * Update the description But, please note the automation is run only after the issue has been created, so the description would be overwritten. This can be limited to update only if the user has…

Hello @NY Welcome to the community!! This is possible with the use of dashboard gadgets. Please create a dashboard and add gadgets for issue counts and display. You can make use of the filters while setting up the gadgets. Please refer to the article from Atlassian regarding dashboards here. This will help you create a…

Helo @Albert Manuel This is possible with the use of Automation. I have done something similar for my cloud instance, though we do not have the restriction for commenting on the closed issues. Please refer to the below screenshot for details of the automation. This can be customised as per your use case. Please share if…

Hello @BrentBot As we do not intend to copy the custom fields to all the stories within the Epic, we need to have a connection/ link between the stories to which the fields are required to be copied. If this link can be defined, then the Automation rule will help in copying the fields from Story 1 to Story 3.

Hello @Warly Silva This can be performed using Automation in the following manner. * Trigger the rule on the creation of an issue * Check that the issue type is 'Story' * Edit the issue fields, set value for Component, copy from Epic issue Please refer to the below screenshots. Kindly accept the answer if this helps.

Hello @Reine Berg Currently, the format does not recognise Re: which proceeds while replying to an email. I would suggest you try the option shared earlier.