Gaurav_0av1h6 Expert

Hello @Allan Vaifale As I understand, you are calculating the difference betwen 2 dates and need only the business days. There is a predefined method to do this using smart values. The general syntax is: {{[date1].diff([date2]).[unit]}} You can replace date1 with now, date2 with the other time stamp and unit with…

Hello @Maverick Schneberger As I understand, the default unit of time for the instance is 'minute'. To handle this, please set the Original Estimate as: {{#=}}{{issue.Story Points}}*4*60{{/}} Here, we are converting 1 SP to 4 H; so if the story has 5 SP, it will be converted to 2d4h meaning 20 hours. Please try this and…

Hello @Dhruva Verma Welcome to the community!! For each new recruitment requirement, you can create a separate issue in the same project. This way you will not need to create a new project for every new recruitment and have all the data in a single project. This will also help you with the reporting as well. --GG

Hello @jeevan Before planning and creating the automation rule, can you confirm the following: * How are the designer, coder and tester for the sub-tasks of a story defined? Are these mentioned in the story? * Is the story transitioned to the next state when a sub-task is completed? These will help create the automation…

Hello @Ranbir Nayal Jira Service Management (JSM) does provide APIs for 3rd party integration. Atlassian documentation for the APIs is available here. Hop this helps. --GG

Hello @Maverick Schneberger Welcome to the community!! In order to convert the Story Points to the Original Estimate, we need to check the default unit setup for the instance. Assuming, that 'Hour' is the default unit of time defined for the instance, the rule can be set as shown in the below screenshots. Please let me…

Hello @Allan Vaifale Please confirm if you still are having the issue with the set up of fields. --GG

Hello @Melle van Keulen In order to scale this up, you will need to create an if/ else construct, where you can check for more values apart from the one mentioned in the example. Could you please explain the need to update the data in the 'Labels' as these can be changed by the user? Also, as Labels ate free text you may…

Hello @Ramesh Maddali In order to create the Automation, you will need either Project Admin or Jira Admin privileges. Also, you will need a free plugin which will provide you with this functionality. --GG

Hello @Melle van Keulen In my opinion, this can be best handled by Automation rules. The rules can be triggered on the issue creation and relevant labels can be added to the ticket. Hope this helps. --GG

Hello @Aswathi D This is strange!! Could you please share the Description which is showing up on the Clones Issue? Is the description of the clone issue matching the description defined in the Automation Rule? Also, please share the Issue Links on the clone issue and the audit logs for the Automation rule. These will help…

Hello @Ramesh Maddali Please refer to the below screenshots for setting up the rule in the project. For further understanding of Automation, please refer to the Atlassian documentation here. --GG

Hello @Aswathi D The action step (pencil icon in blue) of the Automation rule is misplaced. This needs to be placed under the If block where you have the 'Plus icon in Grey'. Please update this and share the feedback. --GG

hello @Marc Rousseau Welcome to the community!! In order to achieve this, you will need a single workflow with all 7 statuses, A-B-C-D-E-F-G. The Epics would be mapped to the workflow, and when you create the board, you can map only the required status to the board columns. The downside of this approach is that the…

Hello @Eminds The project type cannot be simply changed but requires migration to a new project. Atlassian documentation for the same is available here. Kindly accept the answer if this helps. --GG

Hello @Ramesh Maddali Welcome to the community!! As per my understanding of the problem, you intend to send a notification to specific users if the ticket is not updated in the last 2 days. Automation can help you in this case. The rule can be triggered on a daily basis at a pre-defined time which can send an email…

Hello @中込 晴菜 The Type of a custom field cannot be changed post-creation. Atlassian documentation for editing the custom fields is here. As a workaround, you can create another custom field of the new type with a similar name and make use of that. Kindly accept the answer if this helps. --GG

Hello @Aswathi D I tried to create the Automation on my end. Please refer to the below screenshot of a rule which should work for the use case. Kindly check and share your feedback. --GG

Hello @Pavel Kovařík In my experience, we can use 'Time Tracking Report in Tempo' for effort logging but I am not well versed with the reporting capabilities. We had created a similar report using the plugin, 'eazyBI for Jira', where we could view the Epic level and expand the report if required. You may explore this as…

Hello @Martijn Dekker You are at the right place. In the drop-down for fields, please start typing 'Epic' and it will provide you with relevant options. From the options, select Epic Link and provide the required value. Hope this helps. --GG

Hello @Aswathi D Here is what is happening: * A story is created manually, ABC-1 * Automation triggers updating the Description to 'XXXXX' * The story is then cloned, creating a new story, ABC-2 * The Automation does not update the Description but since it is a clone of Story ABC-1; the description is copied giving the…

Hello @Jule Helder We cannot have a default value for description in the Cloud Jira. But having said that, there are alternate ways to do so. * Create custom field * Define the default values for this custom field * Replace the 'Descriptio' field with the custom field on Create Issue screen * Once the issue is created,…

Hello @Martijn Dekker Welcome to the community!! For this purpose, you can create a custom Automation rule. The 3 components of the rule can be: * Trigger: When a new issue is created * Condition: Issue type is Bug and the Reporter is 'Service Now Jira Sync' * Action: Update the issue and link it to the required Epic…

Hello @Aswathi D As per my understanding of the use case, the description of the cloned issues should not be updated. For this, you can add an 'if/ else' construct, check if there are any links of the type, 'clones/ is cloned by', are present, then do not update the description; else update the description as required.…

Hello @Jacob Eriksson Welcome to the community!! This behaviour seems odd!! Could you please share more details on the issue? How are you counting the number of issues/ incidents missing? This will help us guide you better. --GG

Hello @Jason Liu Jira Automation has limitations in terms of the number of issues that can be updated in a single execution and in terms of execution duration. As a workaround, you can create a copy of the Automation rule which works for you and then execute it multiple times. Please feel free to share, if you have any…

Hello @Naiara Torres Welcome to the community!! It is possible for a story to automatically flow/ transition the workflow status using Automation rules. The rules can be customised to be triggered at the occurrence of specific event/s and perform the required actions. Kindly share if you have any further queries. Please…

Hello @Diffusive5915 This is currently not possible on the cloud. There is an open suggestion for Atlassian to make this configurable. https://jira.atlassian.com/browse/JSDCLOUD-8484 --GG

Hello @Gia Jgarkava {Twinit} This sounds like an interesting and easy option, which is available only for the Cloud environment. Are there any plans to release a DC version as well? --GG

Hello @Howell You can set a condition on the smart value {{webhookResponse.status}} and if this fails, you can send an email to relevant users under action. Please let me know if this helps. --GG