Gaurav_0av1h6 Expert

Comments

  • Hello @Benjamin Welcome to the community!! Automation rules can be used to achieve this. The rule can be triggered when the label on a sub-task is updated and the value can be copied to the label for the parent. Please let me know if you have further queries on this. Kindly accept the response if this helps in resolving…
  • Hello @Tran Tien dung As per my understanding, the filed 'Team' is updated with the value 'PIoneer', as soon as the issue is created. If this understanding is correct, then you can achieve this by creating a post function that would help you achieve this on the cloud. Let me know if this helps.
  • Hello @MF フォン I would suggest typing the custom field name in the space provided. If available, it will start showing up. At times when I am unable to find the field name in the drop-down, I start typing and it provides me with the exact field. Let me know if this helps.
  • Hello @MF フォン For creating the Automation, please navigate to Project Settings --> Automation -->Create Rule The first step would be to set the trigger, which ideally is the condition that will kick this automation off. And then, we need to define the required action, which is to send the notification email. Please refer…
  • Hello @Raul Gongora The SLA details like goal time, calendar and JQl are customisable. So if you open up the SLA "Time to first response", it will present the details as shown below in the screenshot. These can be edited/ updated as per your specific requirements. Additional timelines can be added, conditions can be added.…
  • Hello @MF フォン Welcome to the community!! Adding custom fields to Notifications can be achieved through Automation. The Automation can be customised as per the business requirements and would solve this need for custom fields Kindly share details about the use case and I can help you develop the Automation as well. Let me…
  • Hello @Douglas Oliveira I understand that you are using Automation. It would really help if you could share a screenshot of the rule as it will help understand the current implementation.
  • Hello @Dor Asraf Welcome to the community!! The best way to go about this would be to use Automation. The Automation can be triggered when the link between the Bug and Story is created and as the next step, the Story can be transitioned to new Status. Let me know if this helps with the use case or if you have any follow up…
  • Hello @Lee Donovan The ownership can be changed from the following path: Settings > System > Shared filters This would require Admin privileges. Kindly accept the answer if this helps resolve the query.
  • Hello @Tran Tien dung This is possible using Automation. The rule can be created to be triggered on Issue Creation and required fields would be updated as per the business requirements. This is customizable as per your use case. Let me know if this address the concern or if there are any follow up questions. Kindly accept…
  • Hello @Lee Donovan The sysadmin of the instance can transfer the ownership of the filters from you to the new person who would work in your role. This would be the easiest option. Let me know if this helps.
  • Hello @Idham Zainal This is possible using Automation. A simple automation rule can say that if the ticket is not assigned or not worked for 'X' hours, it will be assigned to someone. This can be further customised and enhanced as per the business requirement. Let me know if this helps and if you need further help in…
  • Hello @lprada For the given scenario, it would be optimal to have a custom field that would document the region rather than creating a service for each region. Even for reporting or analytical purposes, the custom field would come in handy.
  • Hello @Mark Kessels Welcome to the community!! To list all Business Projects on a single board, you can create a filter based on the project type. The query can look like: projectType = business You can customize this based on the project types being used. Please let me know if this help or if you have any further queries…
  • Hello @Bindiya Vikram Naik This is possible in Jira using Automation. You can create a loop and create a subtask whenever the condition is met. Here is an example of an automated assignment of tickets based on the CAB value selected which is a multi-select drop down. This can be customised as per your business scenarios.…
  • Hello @Atlassian OneDot The combination is possible. JWM is currently available as a Free and Standard subscription.
  • Hello @Atlassian OneDot Yes, this is possible as the subscription is product specific.
  • Hello @Amane Arin Ariznabarreta Welcome to the community!! This moving of linked issues from the story to the Epic for the story can be achieved using Automation. For this, you will need to store the issue key of Epic in a variable and use it later on. Please refer to the below screenshot for the details of the Automation.…
  • Hello @Karan Patel Welcome to the community!! If I understand your concern, you need only 1 email with the details of all unassigned tasks at the end of the day. Assuming this is your problem statement, this can be achieved by creating a filter and subscribing to it. The Automation would send out a separate email for each…
  • Hello @Brijesh Pathak Jira Service Management (JSM) does provide you with options for all of the queries. * JSM has a user portal that can be used by end customers or people who do not have access to Jira to raise the change * All of these can be covered with a combination of notifications and automation The system is…
  • Hello @Hayley Wood Welcome to the Atlassian community!!! Based on my experience, you would need separate files for each tab of data, though you can add all of that into the same cube. The eazyBI documentation does not specifically say anything about uploading data from different tabs of an excel workbook. The documentation…
  • @Jed Conrad Intalan Absolutely, the reports, in that case, would not be accurate. The sub-task approach would work, and you can have separate SLAs as well. Please accept the answer if this helps solve your query else respond and allow others to share input.
  • Hello @JiaxinWang Welcome to the Atlassian community!! The Team-managed project fields are independent of the global custom fields. Due to this, you will need to create the custom fields again in the team managed project. The steps for the same are documented here. Please accept the answer if this helps solve your query…
  • Hello @Mahmoud Zinji Welcome to the Atlassian community!! You can mention the following persons in comments using smart values for automation: Reporter: {{reporter.displayName}} Assignee: {{assignee.displayName}} Comments: {{issue.comments.author.displayName}} or {{issue.comments.last.author.displayName}} Please accept the…
  • Hello @Jed Conrad Intalan Welcome to the community!! In this case, the SLA for person B would be affected as when you generate the report the ticket is assigned to person B. You might want to consider resetting the SLA on reassignment but that would cause the breach to be missed. This scenario in my opinion would need…
  • Hello @Dinesh Durai For the customization work, you can check with Atlassian partners. The details are available here.
  • Hello @aribeiro Welcome to the Atlassian community!! Currently, new templates cannot be created but the templates can be customised based on your use case. You can create schemes for Issue Types, Screens, Workflow, Permissions etc as per the requirements which can then be re-used for any of the new projects. Please accept…
  • Hello @Paras Sachan Could you please share what exactly would you like to do using Automation? Using Automation the ticket could be auto-assigned or status can be updated or certain field data can be updated, as per the business case. Some of the use cases are documented here. Please let me know if there is some specific…
  • Hello @binay_yadav , in that case, you can clear the sprint fields and add a comment for the user to update the Story Points. But as @Ravi Sagar _Sparxsys_ suggested, this can be really annoying for the users. Though I understand that you are averse of creating multiple automation; but since there are no validators…
  • Hello @Paras Sachan For applying Automation on the sub-task or issues under an epic, you can make use of the ' Branch rule / related issues'. It would help if you could elaborate on your use case, then I would be able to help you with a more precise response. Please accept the answer if this helps solve your query else…