Comments
-
@Géssica Grolli , Eu repliquei o mesmo cenário que o seu em meu ambiente e não tive o mesmo problema, o que é estranho. Nesse caso, eu recomendaria que a pós função fosse refeita ou que fosse alterada a opção de "Run as addon user" para "Run as user" e dentro desse valor inclua um usuário com permissão de admin do projeto,…
-
@Géssica Grolli , Por favor, verifica o seguinte: Se a permissão de "administrador do projeto" possui a project role "atlassian-addons-project-access" Como o user do APP entra nesse grupo, talvez seja essa permissão que ele precisa para fazer a pós função funcionar normalmente. Segue print: Depois disso, faça testes. Se o…
-
@Chris With the help of Zapier you will be able to integrate google forms and Jira to create issue in JIRA. Please find more details on below link. https://zapier.com/app-directory/google-forms/integrations/jira Alternatively you can usr Jira Issue Collectors feature which allows you to easily embed a Jira feedback form…
-
@Géssica Grolli , Provavelmente nesta pós função quem configurou marcou a opção "Do not notify user", ou algo do tipo. Este tipo de configuração parece ser algo feito em algum plugin como o JMWE ou o JWT. Se for isso, recomendaria que olhasse a configuração da pós função e verificar se está desabilitada a possível…
-
@Sari You need to do the following: Create a separate JQL filter similar to this one: Project = XXX AND labels in ("Test1", "Test2") OR project = CCCC AND labels in ("Test3", "Test4") OR project = BBBB AND labels in ("test5", "test6") Save the JQL filter and in "Details" release the permission for the projects that are…
-
@Sari In your board filter you configure the following filter: Project = XXX AND labels in ("Test1", "Test2") OR project = CCCC AND labels in ("Test3", "Test4") OR project = BBBB AND labels in ("test5", "test6") You just need to ensure that you have permission to view issues in projects other than your own.
-
@Mônica Bohrer , bom dia! Este erro ocorre porque na transição entre esses status está configurado um validador. E aparentemente a função regex utilizada está incorreta. Para a lógica ser aprovada, a função regex deveria ser: ([A-Z]{3}[0-9]{3} Onde no campo "Sistema com valor real" aceitaria o seguinte formato: 3 letras de…
-
@Igor Rakic The "All" you are seeing are all tickets created by you or tickets that have been shared with your user. If there is no ticket that has been shared with your customer user, then the empty list view is correct. You really can't see all help center tickets, only tickets created by you and those shared with you.
-
In Jira Cloud you have the RoadMap feature that gives you some of this visibility of hierarchies. This is a feature available from Jira Standard. There is Advanced Roadmaps, which is a feature available in Jira Premium. But I believe you should be able to define your concept of hierarchies using Standard's RoadMap feature.…
-
De forma nativa, não sei se é possível. Sei que usando o EazyBI, é possível extrair esta informação e já alocando em algum report no EazyBI. Nativamente o que você consegue fazer é a combinação de valores por JQL, por exemplo: Project = XXXX AND status = Done AND status = DONE AND status changed BY 60707bd610a0a9006f1addc4…
-
Create an automation using the trigger: issue transitioned. Create a custom user picker field: In automation select the action: edit issue Indicate the custom field and enter the smartvalue: {{initiator}}. Whenever the issue is transitioned Jira will automatically populate it with the transition user.
-
You can use the "Email requested" feature in Jira for your project and hide other request types from the portal. Then, just configure the e-mail requests, according to the link: https://confluence.atlassian.com/servicemanagementserver/receiving-requests-by-email-939926303.html…
-
You can go to "People" and check if these people are registered there as "Service Desk Team" or "Service Desk Customer". If they are, remove them and validate. Some things through project role actions users can continue to have visibility in the portal.
-
You can generate a troubleshooting and support in the System section and check the log why this error is suddenly occurring. With the log, you would know exactly where the problem is.
-
kevin, Algunas actualizaciones más recientes de Atlassian no le permiten eliminar un estado en una transmisión que está activa. Para eliminar un estado, haga lo siguiente: Vaya al flujo de trabajo que desea cambiar; Haga clic en el estado y debería aparecer la opción "Eliminar"; Luego restablezca las transiciones a otros…
-
@Robert Oxford If the transition does not appear, it must be because there are conditions in the flow that prevent it from appearing. You can check the workflow if the transition you want to apply has "Conditions" added and what they are. A quick troubleshooting is for you to use the "Permission helper", it will tell you…
-
Puede verificar si en el flujo de incidentes, en la transición "Crear", no hay ningún rol de publicación configurado para asignarle el incidente. Puede verificar si hay alguna regla de automatización activada asignándole el incidente. Puede verificar que en la pantalla de configuración del proyecto, no está ingresado como…
-
Hey Adel! you can send e-mail> fernando.silva@oatsolutions.com.br
-
You're welcome! I hope they can get this resolved soon. Have a good day
-
Can you verify if this behavior is repeated in another project? If it doesn't happen in another project, you can create a new project by copying the structure of the current one, so you don't lose all the details.
-
Can you create separate queries for each of them and get the result you expect? If you can, you can do them separately and then just unify the queries in a single filter: Type: JQL1: Project = XXXX AND issuetype = XXXX AND status = CLOSE JQL 2: Project = XXXX AND issuetype = XXXX AND status != CLOSE JQL 3: Project = XXXX…
-
If you are a board admin, you can change the filter by entering a new JQL query. Go to the board settings and click on "Edit filter query"; The JQL screen will open, you change the JQL to the new one I gave you and click on "Search". Then click "Save as", repeat the name of the previous filter and put a v2 at the end (just…
-
@Monika Konopska , welcome! Hi Monika! You can try structuring the JQL in the following scenario: Project in (BUG) AND issuetype = BUG AND status != Close OR Project in (PROJ) AND issuetype = PROJ AND status != Close This is the complete JQL that you can follow to extract the information you need. Using the OR condition…
-
In this case, I recommend that you contact Atlassian support to evaluate. If your user has all the profiles and permissions, this error seems to be a bug of the system not recognizing your permissions. The support ticket you can open here: https://support.atlassian.com/contact/#/
-
Si esto fue útil, haga clic en "Respuesta aceptada" para ayudar a otros miembros de la comunidad a encontrar esta solución más rápido.
-
The error is right there in the filter! You need to adjust this JQL to the following: project in ("ST", Project, "Project", "Project", EULR, "project") AND component = LAB AND status not in (Done, Declined, Resolved, Closed) ORDER BY Rank DESC No "Awaiting Acceptance" status. Note that the content of your JQL for your…
-
Does the ticket have a resolution and is it in "awaiting acceptance" status? This doesn't look cool for a scrum board where we're seeing the sprint. But in your configuration, no sprint issue is shown in "awaiting acceptance" status, you can see this because Jira shows the number of issues below the statuses. To see the…
-
Exactly! Go to Board Settings; On the general tab you will have the filter configured; On the "Columns" tab you should see if the status is mapped to any column on the board.
-
If you don't have the SLA feature to configure, you can use something similar to this: Create an automation with the SCHEDULE trigger and make a configuration similar to this. Change the "Stard Date" field to the field you are using to measure the target. I recommend first applying the JQL filter query in Jira so that you…
-
An easy solution that you can configure is as follows: Use the Version Updated trigger: Then add a BRANCH; In the BRANCH settings, select the options "issues fixed in version" and place the current project; Then, still within the BRANCH, insert the actions for editing the "Star Date" and "End Date" fields. In these fields…