Dick Community Champion

Hi @jinu john Welcome to the Atlassian Community. Some practicalities when using linked stories: Blocks - Use this if you're having stories that are truly sequential and the subsequent story can only be carried out when blocking story is done. Think in terms of a recipe of baking cookies. Is blocked by - Similar as with…

Hi @Aleks Vujic Welcome to the Atlassian Community, What you need is a working multi-level-dropdown-form/qaq-p/2176799 described by @Walter Buggenhout Go from his fine post and if things do not work out for you, you can always put a specific follow-up question here. Kind regards, Dick

Hi @Sarfaraz , Thank you for sharing your automation calculation. The error you face comes from a non-recognized referencing of the two custom fields. Please refer custom fields by using issue.customfield_xxxxx. The xxxxx is the ID of the custom field you're referring to. Also refer to the sum of the set of tickets using…

Ah good, you also realized that the custom field Kunde wasn't necessary. Kind regards, Dick

The biggest tip would be to only put test data on a test environment. The second tip would be * To select all of your issues from the blue menu (use: Issues - Search for issues and fill in the search line with project = XYZ) * Use the export button to Export these issues as CSV (use Full Content) * Import these issues on…

Hi @Kristīne Graudiņa This is not possible and not recommended to edit in the Jira source code yourself. You can always go for a custom field (person picker or checkbox) and use an automation to process its information into the ticket (if you can capture your reasoning into decisions that can be executed via automation).…

Gutentag @Ralf Scheller Gibt es bereits einige Fortschritte? Freundlige Grüße, Dick

Hi @Bill Sheboy , thank you for putting these additional gems forward. I hope our mutual tips with their explained rationale can trump the use of scripts that will in fact hinder team growth and agile transparency. Kind regards, Dick

Hi Alyssa, Try custom filters. That would be the place to select the issues that will be used in the board. Kind regards, Dick

Whatever purpose you strive for, unwanted creation of tickets (of all types) in a sprint can be easily mitigated by putting restrictions on who can transition issues, found in the permission scheme of the project at hand, or specifically set in the project's workflow from status "open" into another workflow status. There…

That's.... dare I say it... even worse. Epics normally span multiple sprints. Plopping one of those into a sprint would have an enormous impact on team morale and sense of being in control of the sprint content. A good read on the agile manifesto might steer you into the right direction here:…

Hi @Alyssa Coke Welcome to the Atlassian Community. Are you certain that the epics are filtered in using the board filter? To have them in the side panel, you need to filter them in. Also be sure that the epics are not excluded (same page). You can check that in Board - Configuration - General. Kind regards, Dick

Hi @Tir Neo , Welcome to the Atlassian Community. The answer to your question is quite simple and does not concern Jira. The team is in charge on how many story points they can manage in a sprint. It is the only way in which they can fully commit to getting the sprint done in its entirety. Only by letting them do the full…

I'm curious @Bill Sheboy , could the whole comma-delimited concatenation for storage and subsequent splitting-the-components to remove them consecutively be replaced by the .asJsonArray function? Kind regards, Dick

{{^last}} what's going on here? ^ = Skip (the last), meaning for all other instances in the list, append the comma, except for the last instance.. {{/}}{{/}} two close? is the second one for {{^last}}? Yes. Both the {{# }} and {{^ }} need closure. {{#deletedComponents.split(",")}} we iterate through the value(s) saved in…

If the custom fields were created, it does not guarantee that the numeric value part in their ID is the same. As custom fields are used in automations by their ID, you're bound to have errors if you transfer your automation script 1-on-1. I've been into that alley myself... Kind regards, Dick

Hi @Martin Karlsson ad 1: your condition if issue matches JQL should be component in ( {{deletedComponent}} ) The way it is now, you query for exactly one component. This fails when there are multiple. ad 2: your JSON should be like (no quotes around the smart value and your variable does not end with s) { "update": {…

Hi @Natali Welcome to the Atlassian Community Sadly, a 1-to-1 copy is not possible. The ID's for quite the number of entities could coincide with ID's of already present entities (project ID, custom field ID's, Automation rule ID's etc.). Also the ID's of relative static entities might not coincide (issue type IDs,…

Subtasks throw a spanner in the works. Jira can't just move only the subtasks that are still "open" to the next sprint AND keep the "done" subtasks as part of the sprint that just concluded. It would require another parent story to make that happen. This is in fact exactly the administrative burden you have to accomplish…

Hi @Kratika Shastri welcome to the Atlassian Community It is intended behavior. Big stories with big (lists of) subtasks should be sliced in order to fit into a sprint comfortably. If the team manages to do them within the sprint, they could pull in some other tasks to fill-up the remaining time in sprint and deliver…

Tag @Ralf Scheller , ich versuche dir hier zu helfen, leider auf English, das geht etwas geschmeidiger für mich. :) Your automation starts with a status change in the epic of project 2. The condition would be the status change to status Done. In this automation the triggerissue will always be this epic of project 2. (in…

@Viswa Murthy you did perfectly. In the questions list of this forum, your question will be adorned with a green circle with a tick-mark in it. Only the original poster of a question can do this, so thank you for helping out. Kind regards, Dick

Hi @Sarfaraz , Welcome to the Atlassian Community. In order to maximize your chances on a good answer, could you elaborate on your question. For starters, how is your project put together? How are QA and CT woven into this? It would give this community the information on how to approach the calculation you desire. Kind…

Right on, @Viswa Murthy ! The card layout tab lets you pick and choose three fields to display on backlog tickets. If you mark your answer as "answered", then people with a similar question can find it easier. Kind regards, Dick

Hi @Daniel Murray Welcome to the Atlassian Community. There's actually three 'versions' of Jira: * Cloud * Datacenter * Server The latter has been declared end-of-life and will not receive further updates. It is not the same as the Datacenter Jira version. In addition to this, some software resellers also don't know the…

Hi @Juan Diego Nieto Hidalgo Welcome to the Atlassian Community. you can change the issuetype scheme of the project to include the initiative issuetype. If other projects use the same issuetype scheme, you should copy it first (save it under a different name), then set the projects issuetype scheme to the newly saved one.…

Hi @Łukasz Parafiniuk Welcome to the Atlassian Community. Please share pictures of your automation, including pictures of settings inside the step where you use the user input to find a corresponding epic issue. This gives us the information on how to help you with your problem. Kind regards, Dick

Wrinkles are what makes us human. ;) Dick

Hi @Karoline Friis * Screens contain the fields * Screen schemes contain the screens for the different actions (edit, create) * Screen issuetype schemes contain the screen schemes for a certain issuetype. In the end, the screen issuetype scheme is attached to the project. It is necessary to have it, in order for the screen…

You're right @Trudy P Claspill , I mixed up the change initiative and change request. Where I mentioned epic, it should be change request... I'll change it, to keep things neat and to the point. Dick