Fernando Eugênio da Silva Community Champion

@Darryl St_ Pierre , Legacy automation is being superseded by automation. The automation rules enabled by default for JSM projects are beeing designed in 'Templates' section on your Automation resource. For example: For the Automation rule that sent issues for 'Closed' due inactivity you can use the template "Resolve…

@Tiago Moreira Sadly yes. Other customers added to the project will lose access to the project and you will have to add them again :( When the project is open, it's not possible to remove specific customers or users. Only applying this configuration and manage your customers manually adding each customer into your project.

@Tiago Moreira , you can manage your customers of your project doing this: * Go to Project Settings * Select Customer Permissions * Check the option "Customers added to this service project only by agents and admins" * Click on Save What does this mean? It means that now only people that you add manually as a 'Customer' in…

@Yasmine , you need to adjust your fields on your automation rule To link the trigger issue you need to select the field 'Linked Issues' and choice the link type to link the both issues. To link the Epic you need to select the field 'Epic Link' and you can add the Epic manually or can copy the same Epic of the trigger…

@Yasmine You can create a rule like this: Trigger: Scheduled > Set to one time everyday * Check the JQL Box and select your query, similar to this: issuetype = "Task" AND duedate = now() * Uncheck the box "Only include issues that have changed since the last time this rule executed" After this, just configure an Action…

@econverse , Welcome to the Atlassian Community! The functionality to add new field in Roadmap View (timeline) is not supported in the Basic Roadmaps in the Standard product plan supports adding other fields for filtering. That is only supported in Advanced Roadmaps in the Premium product plan. And for Epic Statuses, it…

@Gabriel Kaneko Atualmente não é possível alterar a cor para este recurso. Já foi aberto um ticket de melhoria com solicitação para este recurso, entretanto não foi algo a ser priorizado no momento. Veja aqui: Ability to Change Color of Days in Column Indicators for Higher Visibility Você pode abrir um novo ticket na…

@Tiago Moreira , welcome to the Atlassian Community! Just to be sure: Do you want to delete the Customer account from your entire environment or delete this customer account for only one project?

@Nate Dickinson You need to add the Jira Product Discovery fields in the 'Additional fields' section on your automation rule. The basic structuture for your use case is: { "update": { "JIRA_PRODUCT_DISCOVERY_FIELD_NAME": [ { "set": { "value": "{{issue.customfield_XXXXX}}" // JIRA SERVICE MANAGEMENT FIELD ID } } ] } } List…

@Salvatore Scibelli , Welcome to the Atlassian Community! The issuetype is still the same 'Test'. To extract the tickets created in this issue type, just issue a query in Jira, something like: issuetype = "Test" If you only want test cases for a specific project, your query should look something like this: project = XXXX…

@nilo soto Currently is not possible to do this. You can disable your project's notifications for when a comment is added, but this will affect all other comments added by this automation user or any other real user who makes a comment. There is a ticket opened to Atlassian suggesting this as a new feature. Take a…

@Yuliia Vyborova This space is for you to change the hierarchy globally. If you just need to add an Issue Type to your project, follow this page: Add, edit, and delete an issue type Let me know if you have questions

@Yuliia Vyborova The hierarchy is defined by Jira's global interface. Click the admin gear icon > Click 'Issue type Hierarchy' and adjust the hierarchy for Jira. Note that changing the hierarchy will affect the Issue Type structure in all other projects where he may be involved

@Yuliia Vyborova Jira displays any issue available to Parent Link an Epic. Maybe you don't have the required permission on the ET project to have an issue of her type displayed. Can you confirm that you have direct access to the EXL project? Also, you should know that an issue can only be set as a Parent Link of an Epico…

@Ntamen kamogne harry Michel If the idea is to share a filter to be able to indicate project roles, yes you can, but you will have to select the project first. So only people in the project role of that project you mentioned could see the filter.

@Taj Zaid Good news! I follow a philosophy that a team that is winning doesn't move lol This Atlassian ecosystem is huge and you will definitely learn a lot from the community. Just fly!

@Taj Zaid , Welcome to the Atlassian Community! Are the fields you want to compare with {{now}} Date fields only or DateTime fields? Another thing, are you using any JQL in your scheduled? If yes, why don't you just put in the JQL that the field ITSM-TERM = now() ? Then you would have a more accurate schedule of events and…

@George , Welcome to the Atlassian Community! Basically, external user will only be able to see and comment on other requests if they have a Jira license associated with their profile and permissions on the target project. Other than that, he will only be able to see and comment on requests where he is being added as a…

@Gabe J_ Beattie If you're be able to create projects of this type, i would recommend you to use 'Jira Work Management' project. With this Project Type you have different ways to see your project issue and details. You have this options at the same time: Board, List, Calendar (With tasks applied into the dates. use 'Start…

@Daniela Salvador , Welcome to the Atlassian Community! If I understand correctly, you have a field in Jira where you put issues that are Acceptance Criteria that must be completed before the current issue can be worked on. Now you want to link the issues you put into the Acceptance Criteria field with the current issue,…

@Bruno Oliveira You need to associate these Forms fields with Jira fields. That's because Forms fields work in a different way that somehow doesn't 'consume' Jira's base fields globally. Go to 'Project Settings' > Forms > Access the form and the field you want, when clicking on the field in Forms you will have the option…

@Bruno Oliveira I realize that your fields are associated with a forms applied to the Request Type. Are these fields configured in Forms associated with Jira fields or are they just fields created from forms without being linked to Jira fields? Also, can you share the Payload you are using in the request? So I can test…

@Katie Planey Welcome to the Atlassian Community! Have you tried to use the Find your field option on your Epics and look for Parent Link field? If you added the field 'Parent Link' in Epic Screens and the field still doesn't appear, the feature Find your field will help you to see where is your field and what actions take…

@Bruno Oliveira , Welcome to the Atlassian Community! To create a request by REST API you need to consider the API for Jira Cloud in Jira Service Management here Also, you need to pass the correct JSON observing the requestFieldValues input format. The doc explain how to do that. If you're not confortable using REST API…

@Ntamen kamogne harry Michel , To give external access for external users only to see the info from your project, you can change the 'Browse Permission' and select 'Public'. Then anyone on the internet with the link will be able to see your issues. You can see more details here: Allow anonymous access to projects Please,…

@Nitish Dua , Probably you don't have a jira-service-management license associated at your profile. Try to access your ticket by this link: https://libertymutual.atlassian.net/servicedesk/customer/portal You will see a Request option in your right side. Click her and look for your issue created. Try to talk with your Jira…

@Hatice Kübra Demirbaş , The best way to know where is your field is using the option Find your field. Just open any issue created at one of these Issue Types, click on 3 dots and select the Option Fiend your field. Select your field and Jira will provide you details explaining where is your field and possible causes he…

@[deleted] No hay forma de evitar la identificación del Assignee. Si extrae el campo Assignee como una columna, en el momento de la exportación obtendrá esta columna adicional de Assignee ID. Lo mismo sucede si pones el campo 'Reporter' en la columna. Jira le dará una columna adicional llamada 'Reporter ID'.

@Andrea_Lawrence Jira does not have an Issue Picker field, so you need to make something like this: * Create a Short Text Field to be able to add the sub-tasks key from ProjectA to be linked with Review issue from ProjectB * Add this field into your 'Transition Screen' and recommend your users to fill this field only with…

@Mateus Luiz Gonzaga Para facilitar que outras pessoas na comunidade encontrem a resposta para situação similar, clica em 'Accept Answer' para aceitar a resposta e impulsionar a visibilidade dela para outros usuários da comunidade ;)