Hana Kučerová Community Champion

Thanks a lot @Monique vdB 

Hi @Giridhar , welcome to the Atlassian Community! Which browser and it's version do you have? Did you try to use another browser? Thank you.

Hi @Johannes Heger (CD) , this is awesome, thank you very much for sharing!

Let me introduce my favorite - chocolate with chocolate on chocolate...

Hi @Alexander Pappert , thanks, maybe I just don't understand you, but are you able to see the reason, why you get kudos? 

@Vero Rivas yes, please try to insert only part of your name - I believe the search is not working correctly, see here, I tried to describe it.

@Jeremy Cejka Plase try something like: List<ApplicationUser> securityUsers = [] ... securityUsers.addAll(groupManager.getUsersInGroup(ALX_FSO)) securityUsers.addAll(groupManager.getUsersInGroup(ALX_FSO2))

@Beverly Braham-Durica would you please share the history of the issue, when exactly all the transitions were performed?

I almost forgot I have sailed on a pirate ship once. It was during our visit of Japan, in Hakone district, which is famous for wasabi :-).

Thank you, it was fun again :-).

It reminds me of our US road trip - we've enjoyed the view from the Golden Gate Bridge very much :-D!

@Jeremy Cejka Thank you - I believe I understand now where the problem is. I'm trying to find the user based on the provided user key. Originally the user names were the same as user keys, but in newer versions of Jira it is something like JIRAUSER12345. So "esanchez" is probably not valid user key and user is not found.…

@Alexander Pappert - I don't think so, I believe these are the correct ones: https://community.atlassian.com/t5/New-to-Jira/ct-p/new-to-jira 

I found out there's at least one another user with the same points - I've informed Atlassian about it.

I'm happy I'm not only one who is confused :-). In my profile I see the exact same numbers 3315 / 3600 - this is definitely suspicious... 

Yes, exactly, please, before the last line like: issue.setCustomFieldValue(securityField, securityUsers) issue.setCustomFieldValue(opsField, opsUsers) log.error(user) log.error(issue) issueManager.updateIssue(user, issue, EventDispatchOption.DO_NOT_DISPATCH, false) I apologize I wasn't clear enough.

@Beverly Braham-Durica Please try to change last line to: return end > start ? Math.round(((end - start) / 1000 / 60 / 60 / 24) as Double) : 0

@Alexander Pappert Please, which discussions/questions did you like? I will send it to Atlassian, so they can check it. Thank you.

There were some problems in the past with the joining, it seems to me it still not working. I'm pretty sure I joined 3 groups recently, but I also didn't get it.

Hi @Manuel Maldonado welcome to the Atlassian Community! I believe you can use JQL condition for this, something like: created >= startOfDay(9h) AND created <= startOfDay(17h) If issue is created between 9 AM and 5 PM, then ...

Looks like the updateIssue is failing, could you please log.error(user) and log.error(issue) and check, if they are not null?

@Beverly Braham-Durica Please try something like this I assumed, that the reopen means, that issue is transitioned to the status Reopen. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.changehistory.ChangeHistoryManager import com.atlassian.jira.issue.history.ChangeItemBean import…

Hi @Jeremy Cejka , 1) Please try to replace issueManager.updateIssue(user, issue, EventDispatchOption.DO_NOT_DISPATCH, false) with issueManager.updateIssue(user, issue, EventDispatchOption.ISSUE_UPDATED, true) 2) Could it be that user jbond is not active anymore, so it so not possible to store him to the custom field?

Hi @Sharon Freij , please try something like this: When: Value changes for Due Date (for all issue operations) IF: Issue Type equals Sub-task For Parent: - If: Issue matches JQL: duedate is EMPTY - Then: Edit issue fields: copy Due Date from Trigger Issue For Parent: - If: Issue matches JQL: duedate is not EMPTY - And:…

@Beverly Braham-Durica thank you. It makes sense to me to store these dates (date of reopen and date of resolution) to the issue to be able to use them in the calculation instead of try to calculate it from the history every time. Can you imagine preparing such a custom fields?

@Alexander Pappert try it again, please. I communicated it to Jacoby - there was a difference between liking comment and liking the original post - it was prior configured to solely reward for liking the original post. Now it's enabled for liking comments too!

@Alexander Pappert Exactly same for me :-) - likes don't work. 

Hi @aokeeffe_guidewire_com , after the quick check - {{SystemsTeam}} and {{FF_Sprint}} seems suspicious. Please try to add it without brackets - SystemsTeam and FF_Sprint Brackets are used for smart values, but this is just simple string...

@Alexander Pappert Thank you, Jacoby looked into in yesterday - it works for me now.

Hi @Beverly Braham-Durica , thank you. What if issue is reopened and closed again later - which date should we use in the calculation? If the time of close is not available as a stored value in the issue (as a custom field's value), we will need to go through the history of issue and find the time of close there, which is…