David Leal_28ge8x Rising Star

I see, no in my case the problem is with the # mark (I tested removing the braces and I got the error). For example:

@Darryl Lee it works I have tested removing the braces, but not adding # mark. I didn't add it, because in the user.Inputs I have several values, but the user selects just one, so it has a single value. My understanding is that this mark is for iterating over several values. In the documentation: Jira smart value -…

@Darryl Lee this is what I did, as a workaround, but according to the REST API specification we can use the section issueUpdates to be able to do a bulk update for issues, I am surprised that the rule doesn't generate an error, so the syntax seems to be correct, but the subtasks were not created. Thanks!

thanks, @Fabian Lim I was able to find a workaround, I guess the only exception is the Clone issue action that allows me to clone an issue on a different project, so It took that approach, and then while cloning to set the values I wanted. My initial approach was trying to look at linked issues after cloning the issue with…

@Tom Williams I don't understand how this could work, but maybe I am missing something, the question indicates the rule is running from a project different than CSONE and if the rule doesn't have a global scope, you cannot find issues in CSONE from a rule running from another project. Thanks fro any help.

Thanks for sharing this approach, it really helps, I have seen other solutions to the same problem but it seems they are not working properly. @Alex Koxaras -Relational- the only comment I have is in regard to the applicability of it, or on which scenario it makes sense to sum the original estimate (durations) up. An epic…

@Sherry Goyal thanks for your post. I have the following use case. to update the original estimate of an epic when any child issue has changed the original estimate value by updating the original estimate of the epic, summing all original estimates from the children's issues. It seems that is the use case you are referring…

Seems to be a clever approach, you mentioned: "automation rules for server", why do you think it would work only for the server and not for Jira Cloud? I have been using the Enhanced Jira Query Tool with Google Spreadsheet, it is a free option and gets the information you want, through the field: SPECIAL: Issue Blocked…

Thanks, @Ste Wright I thought about that too about rule 2, but I want to populate the field Bug Application/Product on Bug creation. If I remove this in the "For" section, then I am not sure if the field gets populated, on Bug creation. Anyway, I don't know why the Bug history doesn't show the Product field has been…

I was looking for something similar, would you share some documentation about this share template you mentioned in your response? @Aravind Koushik Gobburu @shruti gupta @Sagar Bhatia @Mayur Jadhav Thanks! 

@Ste Wright That is what I suspect the Allow rule trigger forces the rule to be executed sequentially. The first one is on issue creation (rule 1), where the field is updated. Here is the rule 1: As you can see Bug Application/Product field is assigned, but also in the second rule (rule 2): The same field is updated. For…

@Ste Wright It is not clear to me the Allow rule trigger option. If I have a rule that is triggered on issue creation updating a field and another rule that is triggered when the same field gets updated, both rules are executed, even if I don't have this option marked. I checked that both rules were executed at the same…

Thanks @Henri Seymour {Easy Agile} it worked, I move my sprints one year and now I an can plan iteration 1.

Thanks @Henri Seymour {Easy Agile} it makes sense, just that it is only grayed out for my Kanban team, for the Scrum teams, the information is the same (the first iteration is in the past). I will do some tests and I confirm it. Thanks a lot!

@Joachim Weichert the link you shared doesn't have all the icons you can assign for different issue types. How to download or use the copy link?, it is not an HTML URL. My intention is to use the icon image for a given issue type in a confluence page, it seems to be an easy task, but it doesn't. Thanks for any help.

thanks @Henri Seymour {Easy Agile} for taking the time to meet with me and give me the opportunity to share with you some of the feedback I have.

@Patricia Francezi_iDev_ sorry I don't see it on the thread of your response. I updated my answer, finally I was able to find the root cause in my example. It is confusing, because the issue is not the date format, but the fact that the value to assign is null. This is what I found out. 

The error doesn't help too much, it is not really about the format of the date (in my case at least), but the fact that the value to setup is null, so it complains about the format of the date, which make you thing it is something related with the format, which is not. In my real case, I was updating the start date inside…

@Bill Sheboy it worked, thanks so much!!!

Thanks @Bill Sheboy I guess you mean Filtering smart value lists, but the example provided is for taking an specific action, for example extracting a specific field if the condition matches: {{#issue.comments}} {{ if(isInternal, body) }} {{/}} but I think what we really want is a subset (a truly filter), I don't know if…

Thanks @Bill Sheboy I guess I was able to follow you. I tested and it worked. For the advanced compared condition I obtained the list of states, then join it, and using the condition contains to find either active or future. That was my understanding from your recommendation, but may you had in mind something different or…

Thanks @Bill Sheboy it makes sense, in my case it worked, I trigger it manually with an issue that has just a single future sprint assigned. Initially I tried to have everything in an a single advanced branch, but it didn't work, because inside the Advance Branch you can add only add: New Action and New Condition, and the…

Thanks @Alex Koxaras -Relational- for your response, I am not Jira Admin, only Project Admin, so I am not familiar with the events functionality. What I read is that you can associate a notification, but it is for sending emails only and it would not be an effective notification mechanism for my project. I am considering…

I had several errors or mistakes in my initial approach: * I used status, but the field is state. * I though the brach can have multiple conditions, but doesn't happen, so after re-fetch, the next condition: start date is empty is never reached, so I need to create a second branch. It looks to me inefficient, but it seems…

@Karoline Rezende Ramos would your share the resulting rule (screenshot), it would help other members of this community on how to solve a similar problem. Thanks

Thanks @Sara Hekmat yes, you are correct, with Jira Advanced Roadmaps (JAR) you can achieve it in a very elegant way, adding a third hierarchy via initiatives for example. Maybe in that case it makes more sense to use the third level, because you can connect your epics to your initiatives and have the board of your…

Thanks for your response, finally I was able to visualize the third level. In my opinion it is not really a third level, but basically a way to connect the epics with a third board. That links some epics with the team boards. I got it, the thing is that I don't see the benefit of doing this, but I am a beginner, I am…

Thanks @Kelly Arrey and @Nic Brough -Adaptavist- I got the idea, and I had it in mind, on my project design, but I don't think the Team field, allows multiple values, where as components allows it. It seems to be a mess at first, but not really, because I mentioned we are implementing SAFe, so we can have epics (emulating…

same error, did you try on your end? just to make sure it works in another Jira instance. You can find your custom field via: https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names and search by Start date. Thanks,

I guess this is one of the options I tried before, I tried it again and I am getting the same error: TTSB-11 (The Target start must be of the format "yyyy-MM-dd" (customfield_10022)) Regards, David