Dick Community Champion

Hi Tom, As reporting is required for both Dev and QA team, you should give them each a project to work in. It is a prerequisite for Jira to provide metrics of both teams. An overview of tickets from both projects can always be generated using a board that filters in the issues of both projects, so that's not a reason to…

Hi @Ann Rumenapp You need to trigger on issue creation, then check if it's of the change request issuetype and check if it has a parent. If it does have a parent, you follow up by an edit action in which you fill the triggerissue's special field. You should be aware that users might also set the parent link of a change…

Hi @Tom Garland Thank you for this well-described question. You're right in choosing two individual Jira projects that individually can be monitored for output. Key in your approach is thus: how do we produce the corresponding QA ticket in the QA project? This is where Automation is your friend. You can: * Have an…

Hi @Nissim Ariel Tuncay refers to a previously made filter that holds the tickets of all the projects. This filter is made from the Issues - Search Issues menu in the top blue bar. You can save the results and it becomes the filter that Tuncay refers to. Kind regards, Dick

Hi @BiruteK Welcome to the Atlassian Community I'm sorry to say that by restricting yourself to two custom fields, you're setting yourself up for database disaster. As @Karan Sachdev mentions, use cascading select list. This is the only way that reports derived from it will be interpretable in only one way. 

Hi @Eran Roiter As per Atlassian Documentation on smart-values-date-and-time/ the expression {{sprint.startDate.plusDays(14)}} //returns 2020-08-20T23:27:54.2+0000 I admit, it is the startDate, but looking at the result, this is a DateTime expression. Would your custom field accept that as a date? You can break-up your…

Hi @Ilgar Gurbanov Welcome to the Atlassian Community This is a css bug that should be reported to Atlassian Support. This forum cannot help you any further with this. It's good that you tested this on multiple browsers with cleared cache and cookies. Do mention that in the ticket. Kind regards, Dick

if it's not like the manuals for you, it's best to bring this to the attention of the developers by submitting a ticket to Atlassian Support.

If you need the complete array of components to be copied over, the JSON code would be like: { "fields": { "components": {{issue.parent.components.asJsonStringArray}} } } Where fields is a shortcut for calling update with the set operation. 

First step would be to share your current automation with this community then. It should be triggered by on create (or with an extra automation on field change, depending on your helpfulness to your users). Followed by making sure it's an epic you're working on by the conditional issuetype = epic. Then the action would be…

Hi @Lars Magnus Fylke Are you an administrator of said board ? That's a pre-requisite to be able to edit it. Kind regards, Dick

Hi @Velizar.Velizarov Could you mark this as an answer, so that others with a similar problem can find it easier please? Thanks a bunch, Dick

The quoted documentation holds one really big piece of code with the Supported fields & Operators. There you can read on lines 39 to 52 that there are in fact three operators available for the components field: add, set and remove. Hope to have given you a fishing rod instead of a fish :) Dick

{ "update": { "components": [{ "add": {"name": {{Domain.asJsonString}}} }] } } In this example, Domain was defined as a variable using Create Variable in Automation. This should also work with "somethinglikethis" 

Hi @Sharmila Hiranandani The {{smart values}} give you an opportunity to construct the result into an output string Also {{now.diff(issue.created).weeks}} is a nice example where the output is the number of weeks ago that an issue is created. That's only a hair apart from your request. Combined with conditional…

Hi @Lars Magnus Fylke The ebil devs of Jira past might've put this under board configuration. :) Kind regards, Dick

Hi @Sharmila Hiranandani Basic arithmetic with dates is described in automation/docs/jira-smart-values-date-and-time/ kind regards, Dick

Hi @Velizar.Velizarov Welcome to the Atlassian Community You would need to use the JSON part of the automation to update the component/s field (which holds an array of strings). You can find documentation on this: automation/docs/advanced-field-editing-using-json/ Kind regards, Dick addendum The above is for both cloud and…

Ah, I read that wrong and thought that the v3 of Guilherme in its whole was the newest compared to the v1 in your url. I should've know better <3 Dick

Oi @Bill Sheboy , that's even an older version of the API. Wouldn't it be better to see if a similar function is available in a new(er) version of the API ? Kind regards, Dick

Hi @Guilherme Baccarin , Welcome to the Atlassian Community. It must be the case that Atlassian closed the door on you. As found earlier: https://community.atlassian.com/t5/Jira-questions/How-to-get-all-Teams-in-JIRA-via-the-cloud-rest-api/qaq-p/2347367 one could describe external usage of this exact endpoint as a hack,…

Hi @Alex Pytlak , Welcome to the Atlassian Community. You can either use a single-project and set-up a field that you use to differentiate between the 10 locations, or use 10 separate projects In both instances, you can look at these projects using a plug-in that allows for the summation of individual tickets across the…

Hi @SSU Yes you can. With the trigger issue being the story (I assume this is what you call the child of the epic to be updated), you can refer to its parent (using epic link, or depending on your version of Jira, the parent link). Then you can lookup the array of issues that are the children of said epic and find the max…

Hi @Eran Roiter Why not make a small web-page with the (numbered) pictures and use the issuecollector function of Jira to have your people vote for the number (dropdown Jira custom field)??? You get your answers convenient together, nobody can sneak in a double entry, pure joy! Kind regards, Dick

Hi @Rajkumar Rajamanickam , It is always possible to clone the issue to a "control Jira-project" and do the above trick in that project, leaving the original issues untouched. The original issues should be assessable (selectable!) through the linked issue fields. Penny for your thoughts on this :) Dick

Hi @Rajkumar Rajamanickam Consider this work-around: If you have a regular automation that triggers on edits to your custom field and then edits i.e. the Resolution or Fix Version of the issue to a certain value, the changed operator could be used in addition to a poll of that certain value to yield you the desired issues.…

Hi @Kevin Blake From the top picture you posted, "done" isn't the last column in your board, like you told @John Funk . I understand the pressure you're feeling as you're currently encounter this problem with your team. To take things into your own hands, I would re-suggest John's approach: * Have you tried his solution,…

I'm sorry to hear that the outcome isn't exactly what you desired. Going 180: can you perhaps avoid the initial problem by having the stuff that ends up in the "everyting else" swimminglane also inside a story, and perhaps give that a colour to distinguish it from the regular stories? Kind regards, Dick

If you ie have used issuetype epic for the testplan, you can do: "Epic Link" = EPIC-123 OR parent in childIssuesOf("EPIC-123")

In your case, the selection was Stories. That means that all issues that are not stories or their subtasks are gathered in the Everything Else lane. Hope this gives you some insight as to how the interface works. Dick