Fernando Eugênio da Silva Community Champion

ASAP

@Laura Cella Martins , bem vinda à comunidade Atlassian. Para filtrar issues onde um campo personalizado está vazio, basta você adicionar o conteúdo IS EMPTY depois de selecionar o campo na JQL. Por exemplo, vou usar o campo "Due Date". JQL: "Due Date" is EMPTY Essa query vai trazer todos os casos em que o campo "Due date"…

Hi Victor, welcome to the Atlassian Community! You can find the list of available partners in Brazil by going here: https://partnerdirectory.atlassian.com/ In Country, just indicate Brazil. I am part of OAT Solutions, Platinum Partner in Brazil. If you are interested, please send an email:…

@Aykan Inal Only people with "site-admin" permissions can create and manage groups in Jira Cloud. If you have this permission, follow these steps to create and manage groups: https://support.atlassian.com/user-management/docs/create-and-update-groups/

@Yuri Cardoso da Silva , welcome to the Atlassian Community. You may be able to extract this data using the following JQL: status changed FROM "In Progress" DURING ("2022/04/01", "2022/04/30") Jira will list all issues that have gone through "IN PROGRESS" status during this period. You can see more details…

For this to become something standard you need to do the following: Access the board settings; In the "General" section, you will see the "Saved filter" option. You need to change the filter contained in "Saved filter" to the filter you created. Do the following: Save the filter you want to assign to this board; Release…

@Martin You cannot see this option because you are using a User picker (multiple users) field. You must use a User picker (Single user) field. Then from there you will be able to use the resource to filter the group of users that the field should display.

Você pode ir em: "Configurações do projeto"; "Automações de projeto" ou "Automações". Chegando lá, você verá as automações que você possui configuradas no projeto. Então você pode avaliar se há alguma automação que está fazendo ações nos campos "End date" ou "Start date". Vale a pena também avaliar se você possui o app…

@Taynara de Cássia Gregório , bem vinda à comunidade Atlassian. Isso parece ser fruto de alguma automação agendada, que está executando este update nos chamados e as notificações estão sendo enviadas por configuração de automação ou do projeto. Primeiro eu recomendaria que você buscasse no projeto se existem alguma…

@Martin You must do the following: - Create a field of type User Picker (single user); - Then click on "Edit context and default value" for this field; - You will see an option called "Edit User Filtering"; - By clicking on it you can point to a group where this field will only show users present in this group. After that,…

@Dennis_H This filter is correct. If you don't want subtasks to appear on your board, you should use a JQL in one of the following ways: AND issuetype != Subtask OR AND issuetype not in ("Subtask") See more in: https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/

Welcome! I´m from Brazil ;)

@Rodrigo Kleinert , welcome to the Atlassian Community! To delete Custom Fields follow this process: https://support.atlassian.com/jira-cloud-administration/docs/edit-or-delete-a-custom-field/ A suggestion: If the field you want to delete has value in some issues in projects in jira, this value will be lost. I would…

In this case, if you want the field: "Required Accounts - Contractor" to make your automation work with more than one option contained, you should use the following JQL: "Required Accounts - Contractor" IN ("LastPass", "AWS") If any "Required Accounts - Contractor" option should make the automation work, you should use:…

The JQL for checkbox fields are: "Required Accounts - Contractor" = "LastPass" You are using > Required Accounts - Contractor" ~ "LastPass" Understand the difference of ~/= I think the problem may be there. I would recommend that you first assemble this JQL using the "Search issues" feature in Jira. When you get results…

Try the following: Click on Manage Apps; Check if the app is still in the list of apps in the environment; If yes, click to expand the app and click "Unsubscribe" or "Uninstall" if you want to uninstall.

You are using "Required Accounts - Contractor", but Jira is reporting that the "Required Accounts" field is the one experiencing problems. Can you confirm what the correct field name is? Also, is it a select list or single text field? This will help to better identify the cause and help you.

@Miriam Ofstein Instead of using the direct action "Assignee issue"; Try using the "Edit Issue" action; Put the field "Assignee"; Click on the 3 dots located in the right corner of the field; Select the option "Copy from..."; Click on "Copy assignee from current issue"; Change the value of "Field to copy value from" to the…

@Carlos Andres Ortiz Lambis Te recomiendo que eches un vistazo a los permisos del proyecto. En concreto sobre los permisos de: Editar problema; Modificar reportero. Si su usuario tiene estos permisos en el proyecto para realizar tales acciones. Si esto es totalmente correcto, verifique en el "Ayudante de permisos" lo que…

Oi, Leila! Não sei se é o mesmo caso que foi descrito em outro momento neste link: https://community.atlassian.com/t5/Jira-Software-questions/Filtrar-apenas-issue-quot-related-to-quot/qaq-p/1982288 Se você pensa em algo diferente disso, pode dar mais detalhes do resultado que você espera obter? assim conseguiremos te…

Correct! In this case, what you can do is remove the invite made to this email and send a new one. Or pass your URL to access the site and ask the user to enter their email and password, as if they were going to access jira. Then it will have the option to "Request Approval" to integrate your environment. You will be able…

@Michael Arun Padamutham Sometimes the guest email falls on an Atlassian block list for some reason and this email does not receive any notifications from Atlassian or Jira. So if he doesn't get the invite to join your jira, maybe that's the case. You need to open a support contact via the…

That's exactly what I'm trying to clarify for you. In Jira Cloud, the only way to make a field stay on screen regardless of whether it is editable or non-editable. It's including it in the "Description fields" in the issue layout configuration

@Ada , welcome to the Atlassian Community! You can use a JQL condition for this case, try something like: JQL: "customfield A" is not EMPTY OR "customfield B" is not EMPTY So Jira will read if any of the two fields are filled in the ticket and will work normally without having to split it into 2 automations. Try this and…

@Jeffrey Bistrong For that case, you must make these Issue Layout changes. Go to Project Settings; Issue Layout; Drag the field you want to the "Description Fields" section. They will assume the position in the middle part of the screen and will be displayed even if they are empty.

@Jeffrey Bistrong In the case of Cloud, if the field is only on the "View" screen, it will be visible to you in Jira when it has a value filled in. So if you have an automation or flow rule that fills in this field that is only on the preview screen, when it has a value, it will be available to you where you expect it to…

@Bruno Mesquita dos Santos , welcome to the Atlassian Community! In your create ACTION, the "Summary" field cannot be empty. You must put a value on it or make it copy from the issue being carried over. Also, the "Reporter" and "Labels" fields seem to be mandatory in creating this other issue, but they are not on the…

@Bryan , Two things could be the reason for this problem: 1: The board filter may be hiding the view of sub-tasks. Your board filter needs to consider subtask issues. 2: The "Resolution" (green) status of the subtasks must be mapped in the column that has the green color on the board. Then insert all the green statuses of…

Exactly, Jay! It may be possible to add more than one condition of this type using some app, like "Jira Misc Workflow Extensions". It's a great app for automations and flow rules in general, but it has costs. Natively, using the REGEX that I gave you, you will be able to validate only one email template and not two.

Hey, @Lewis Martins . Please, verify if this answer helps to you: https://community.atlassian.com/t5/Jira-Service-Management/JSON-body-example-that-links-an-Insight-object-to-a-JSM-issue/qaq-p/1986713#M101743 "customfield_XXXXX": [ { "workspaceId": "WORKSPACE_ID", "id": "WORKSPACE_ID:OBJECT_ID(NUMBER)", "objectId":…