Comments
-
Team Managed projects don't have the Component functionality at this time. Team Managed projects have two custom field types that support multiple value selection (if that is what you need) - Labels and Checkbox. I've never tried to import Zephyr data before, so I can't advise on which option would be the best, nor exactly…
-
Hello @Andrei Aleksandrov Welcome to the Atlassian community. To select issues under a list of Epics you should be able to use this JQL: "Epic Link" in (comma separated list of Epic issue keys) You can use that filter as the basis for the Pie Chart Gadget or the Two Dimensional Filter Statistics gadget and use Epic Link as…
-
Hello @Mahantesh Hooli Welcome to the Atlassian community. Please provide a screen image of the rule and the details of the action where you are using JSON code.
-
Hello @Philip Wilson Welcome to the Atlassian community. There is a built in "Component" system field which is included in Jira Cloud. However the Component functionality is available only for Company Managed projects. In Jira Cloud there is another type of project called a Team Managed project. You can determine which…
-
Oui, c'est la vue que je voulais. Notez que l’état Termine n’est pas mappé à la colonne la plus à droite. Cette colonne est intitulée « Frozen». Dans Jira, à la fin de votre sprint, seuls les tickets qui se trouvent dans la colonne la plus à droite sont considérés comme terminés. Les problèmes dans les statuts mappés sur…
-
I don't know. I suggest you create a version of the rule that uses a Manual trigger and only prints the result of the calculation to the Audit Log, and then trigger the rule from issues created outside of the 9 am to 6 range and review the results.
-
Hello @cmclean If you are receiving the email because of the Notifications configured for the project, there is no way to in Jira to have it not send you emails from a particular user. If you change the actor of the rule to yourself, then in your profile settings you can uncheck the box that says get emails for actions you…
-
Hello @Dean Losurdo What are the Types for the source and destination projects? You can find that information in the Type column on the "View all projects" page under the Projects menu. What are the field types of the fields that are not copying over? You said it is not copying "some" of the information from the fields.…
-
Hello @[deleted] Welcome to the Atlassian community. I believe that is possible. However it requires a multiple-project scoped rule, and those can be created only by a Jira Administrator. The basic rule structure would be: Trigger: When issue status changes Condition: Issue is in the JSW project For each: Linked issue in…
-
Great! I have to credit @Bill Sheboy with reminding me about that trick recently. If your problem has been solved, please consider clicking the Accept Answer button.
-
Vous pouvez déterminer si le champ Résolution est défini en affichant directement l'un des problèmes et en recherchant une coche verte à côté du statut. Pouvez-vous fournir une image d'écran montrant le mappage des statuts aux colonnes de votre tableau afin que nous puissions voir si le statut est mappé à la colonne la…
-
Hello @Jared Fusedale In JWM projects Subtask types of issues are shown as a group under their parent issue, regardless of the statuses of the individual subtasks. The Subtasks will not be shown separately in the column that matches their status. Subtasks are denoted on the card for the parent issue thus: You can click on…
-
Hello Jared, There is not a native report that will provide that information. You can't get that information from a single query. You could create multiple queries to get the list of issues that match each pairing of user and destination status by using the CHANGED operator.…
-
Sometimes Issue Created rules are triggered so fast that not all the data has actually been recorded in Jira yet. Try adding a Re-fetch action before the step where you create the new issue.
-
The solution above is very simple. Login to your Jira instance. Make note of an issue key in the project of interest. Duplicate your Jira browser tab. Substitute in the text from the document from the slash following the base URL. Substitute in the issue key of an issue from the project. If the user can get to Project…
-
Hello @Ireneusz Michalik I have added a tag to your post to raise it to the attention of Atlassian Team member who can check if your email address has been put on the suppression list. They should respond to you in the next day or two.
-
Hello @Jose Antonio Quesada You can use the method described here to output all the fields for an issue in the project. https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ In that output you will find a block that gives you information about the project including the project ID: "project":…
-
Refer to the answer I provided. Use the businessDays option instead of abs.days If you want it to always be a positive number then use businessDays.abs As per a note farther down in the document "BusinessDays (business days are considered to be Monday to Friday, 9am to 6pm)"
-
Their listing claims that it does. Maybe you should contact the app vendor about that.
-
For Custom Fields a Jira Administrator can modify the custom field definition to set a default value. Refer to: https://support.atlassian.com/jira-cloud-administration/docs/configure-a-custom-field/ For the Component field specifically you can't set a default value with native Jira functionality, as it is a System field.…
-
If I understand correctly you want the date difference calculation to exclude weekends and your current calculation is: {{now.diff(issue.created).abs.days}} As per the documentation concerning smart values for date and time: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ ...if you look…
-
If my suggestions have lead you to a working solution, please consider marking my Answer as Accepted.
-
Hello @Marcus_palm Welcome to the Atlassian community. Instead of using {{Description.body}} use {{issue.Description}} Comments are a special type of entity that have multiple attributes such as "body" and "author". The Description field doesn't have such extra attributes. Also, within a rule when you want to access the…
-
You can create a quick filter for your board and activate it so that only Epics and the issues not linked to Epics are displayed. Then activate that quick filter when you want that view. issuetype = Epic OR "Epic Link" is EMPTY
-
Helo @Vanessa Johnson The content of your questions doesn't seem to have anything to do with the title of your post. Which question are you trying to get answered?
-
I have not tried any cost-free solutions. Gitlab for Jira Cloud is free. The listing for the app says that it works with self-hosted Gitlab. If that was the app you were using then you should consult with the vendor of that app to get more guidance.
-
Jira's default issue hierarchy is Epic (level 1) |-- standard issues types (i.e. Story, Task, Bug) (level 0) |-- sub-task issue types (level -1) Jira automatically recognizes a parent/child relationship between these issue when the "standard issue type" issues are added as children of an Epic. And Sub-tasks can be created…
-
I am not a networking expert nor do I have any experience with Cloudflare. I recommend that you consult with experts in those technologies to confirm conclusively that the Cloudflare configuration is not blocking the traffic from Atlassian Cloud to your Gitlab instance. You may also want to consult with the vendor of the…
-
Yes, thank you, that is the screen I wanted to see. Lastly I need the answers to these questions: Is a Task every linked to more than one Story? Is a Story ever linked to more than one Epic? Also, I have two related questions for you. Is there a reason you are using generic issue linking to relate the Story issues to the…
-
Thank you for those images. Based on that information you are using the generic issue linking functionality to create the relationship between the Task and the Story. Can you now provide an image from the Issue Linking page? Access that by clicking on the gear icon near your avatar, then selecting Issues. In the new screen…