Comments
-
For all the issues in that project that you don't want the users to see you also need to assign a Security Level to those issues and it needs to be a Security Level that does not include those users. Security Levels are used to limit the visibility of an issue. If no Security Level is assigned to an issue, then it is…
-
Is this for a Team Managed project or a Company Managed project? Which of the specified issue types in the condition does the new issue match? Is the rule getting triggered? What information is available in the Audit Log for that execution of the rule? I created a rule for a Company Managed project using the Issue Created…
-
Hello @İsmail Özçelik What is the type of the field?
-
Hello @Anders Hebert For a Company Managed project it is not possible to set a default value (template) for the Description field with native functionality. There is a workaround described here that involves creating a custom field where you can set a default value, showing that in your Create Issue screen, and then…
-
Hello @Cynthia Kallas Welcome to the Atlassian community. In the second image you appear to be searching your backlog screen for a specific issue - SF-8442 - and it is not being found. What is the Status of issue SF-8442? Can you show us the Columns/Status mappings for this board?
-
Hello @Cyril James Please show us the complete automation rule you created. Additionally, exactly how is the cloning process being executed? Does a user open an issue and then select the "Clone" operation from the ... (additional actions) button? Or is the clone being created through some other process?
-
Hola @Gladys.Fernandez , Lo que describió es la funcionalidad de vinculación de problemas. Crear un vínculo entre problemas de esa manera no inicia automáticamente ningún otro cambio en la funcionalidad. No existe ninguna funcionalidad integrada que impida un cambio en un problema basado en la información de otro problema…
-
Hello @Oday Rafeh You cannot change a Team Managed project to a Company Managed project. You have to make a new Company Managed project and move the issues from the Team Managed project to the Company Managed project. Data may be lost when you move the issues. Review this documentation on the topic.…
-
Another thing to check is that the Lookup Issues action is actually returning results. You can add a Log action after the Lookup Issues action to print out how many issues it found using the smart value {{lookupIssues.size}} As Bill said, smart values need to be exactly right. In your Log action for the Lookup Issues sum,…
-
Why does your team want to see old completed issues on the board? The completed issues column will eventually include many issues if it shows all the completed issues, and the board will be less efficient to use. It is not possible to force all the completed issues to display on the board in a Work Management project. You…
-
Helo @Flavie Henry The Browse Projects permission gives the specified users the ability to see the project in the "View all projects" screen and to see the issues within the project. It does that for only the projects where the user is granted that permission. If the user is not granted that permission in other projects,…
-
Please show us the details of your automation rule. Where I used {{triggerIssue.approval}} I meant to use approver. However, in that spot you need to substitute the actual name of the field that you use to document the approver.
-
This is a feature of the Work Management project. It applies to both the Team Managed and Company Managed varieties of this type of project. What problem are you trying to solve by keeping completed issues visible on the board?
-
Hello @Oday Rafeh Your first image is from the Project Settings > Notifications page for a Company Managed project. Your second image is from the Project Settings > Notifications page for a Team Managed project. Company Managed projects use Schemes for a variety of configurations (Notifications, Permissions, Workflows),…
-
Hello @cecile Tarroux Even though the issue types have the same name (i.e. Task) in a Company Managed project and a Team Managed project, the one in the Team Managed project will have a different unique ID associated to it. I created a multiple project rule to run against a Company Managed project and a Team Managed…
-
Você pode aplicar a definição de sua escolha a esses itens. Suas definições parecem razoáveis para mim. Existem muitas opiniões disponíveis na internet sobre as definições de "história de usuário" e "tarefa" sem considerar Jira. Realmente depende do tipo de trabalho que você está acompanhando e de quem são seus…
-
You don't need "{{#debug}}". Use the Log action to print out the smart value to the Audit Log when the rule executes. You can add some explicit text so that you recognize the output in the log. The output in the log would then look something like this.
-
Hello @kumari. dvipa For a Work Management project completed issues will be automatically hidden from the board when they have been done for 14 days or longer. This is by design and not configurable. The idea is that if the issues have been done that long then they no longer need to be seen on the board. The issues still…
-
Adding to this... Did the user create an account using a domain that you have claimed; i.e. yourCompany.com?
-
Hello @Kevin Smith You are right that it is not possible at this time for end users to create additional filters for custom fields that appear like the built in Epic and Type filters (where there is one button for the field and it automatically presents the possible values of that field for you to use to filter the board).…
-
Hello @Maria Fernanda Costa de Melo Welcome to the Atlassian community. Have you tried to construct this automation rule? Can you show us what you have so far? The basic structure of the rule would be as follows: TRIGGER: Issue Transitioned From Status: To Do To Status: In Progress ACTION: Edit issue Field to edit: Start…
-
Olá @João Pedro Galvão de Oliveira , No Jira do ponto de vista funcional e técnico não há diferença entre uma Tarefa e uma História de Usuário. Ambos são tipos de problemas de “nível padrão” e a funcionalidade nativa do Jira os processará de forma idêntica. --- Hello, In Jira from a functional and technical point of view…
-
Hello @Monika Worcester Welcome to the Atlassian community. Please show us the details of each step in your automation rule, and also please show us the Audit Log details for an execution of the rule.
-
Hello @Douglas Oliveira Costa Welcome to the Atlassian community. Are these issues in a Company Managed project or a Team Managed project? That information will show at the bottom of the panel on the left when you are viewing the project board. When a rule does not work the way you expected, you need to review the Audit…
-
Hello @tbundy Have you tried to construct this automation rule? What do you have so far? You could use a Schedule trigger with a JQL statement to select all the Feature Launch Tracker type issues that are in the Canceled status. You could then add a For Each: Related Issues: Sub-tasks step to select all the sub-tasks of…
-
Hello @MURUGESH S Please provide more information about your use case. I don't understand what you are trying to do. What is the name of your custom field? What type of custom field is it - text, number, selection list, ...? Most custom fields can be used within JQL statements so that you can select issues based on the…
-
Hello @Mark_Gallier Here is the documentation for the Log action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action
-
In order for the gadget to report on "Resolved" issues in the time period you specified it would be looking at the Resolved date/time stamp. That timestamp is set automatically when the Resolution field is set. The Resolution field should be getting set when your issues move to a green/done status, and the field should be…
-
@Bill Sheboy I think your example rule has an error, if you are trying to sum up from child issues to the parent Epic. * trigger: value changes for "Estimated Mandays" field * condition: issue type equals Task * action: lookup issues using JQL* parent = {{triggerIssue.key}} AND issueType = Task <<<<< * branch: on Epic…
-
Hello @Flavie Henry Welcome to the Atlassian community. You should not be using the atlassian-addons-project-access role. That is not a role that is intended to be assigned to users. It is used only for granting access to the apps that you add to your Jira instance. Is the project the new group needs to access a Company…