John Funk Community Champion

Thanks for the clarification. You can do that if you like. I still do not know what you are trying to accomplish. Do I agree with the reassigning the Assignee back to the Developer when it is already done? No - he was not the assignee of the last function performed on the task. Of course, I also don't like the idea of QA…

No, Assignee should be a single person, not a team. It is the person doing the actual work. The whole team is not doing QA on that single issue - only one person is. So that should be the person in the Assignee field. What is it that you are actually trying to accomplish? 

Hi Juan, If I remember correctly, there was an announcement that Automation for Jira was being absorbed into Data Center, and there would be no need for installing it as a separate app. Maybe that is what is happening with version 10. You should be able to search for the announcement. 

I would 100% disagree with this approach. If you need to run reports about who the developer was, then create a custom user picker field to capture the Developer and run your reports from that. But in no way is the assignee at the end of the process to be considered to be the developer who worked on the issue. 

The assignee is the person who is performing that step of the work. A task/issue will go through potentially several steps on it's way to Done. So different people will perform different steps at different times. That person is the assignee for that work in that step. If the last step is for QA to test and deploy, then the…

Hi Colin, You can't export from the quick filters. You would need to apply the same code from the quick filter to your filter and export the results from the filter. 

You should log out the values after the two steps to see what it is getting. One after the original lookup issues and the second after the branch. 

No, don't use Current Issue for the Branch - use JQL for the Branch. And put the same code in your Condition as the JQL. 

Hi Seenivasan, How are you wanting to do restrict it?

Yeah, that last step where it is linking the issues is not restricting it to the issues found in the Condition - the Condition is just making sure there is at least one that matches. I think I would add a Branch there with JQL and use the same code from the Condition Then move the Link issues action under the Branch. Give…

Great! Thanks for sharing that. 

Hi Purnendu, Jira should already capture the email response as a Comment if the user responds to the email coming from Jira and if they leave the issue key in the subject of the email. 

Very much needed - thanks!!

Awesome changes - thanks @Sam Knight !!

Hi Aas, There is ScriptRunner Connect app that would be perfect for that. 

Hi Jiw - Welcome to the Atlassian Community! No, I would not assume that the ultimate assignee is the person who fixed the bug. This is just following the normal flow as it should. I think it is great as you have it. 

Hi Kashif, No, not to the actual Reporter field. However, you could create a new custom field of a User Picker (Multiple Users) type. Then you could store the additional users there. You could then add the custom field to your Notification Scheme for the project to notify the users in that field. 

Can you share your final rule with details? 

You should be able to change the Create screen to add fields. 

Great! Glad to hear.

You should just need the Browse Project permission in the parent project. 

Good - glad to hear you were able to move forward. 

In those cases you might want to have separate projects. Totally up to you. 

Great! Glad it is working. 

The bad idea is having multiple fields with the same name, not the algorithm. And there are other questions above for you to answer. 

Is the existing board one that you want to limit the issues? Or show all issues?

Hi QA - Welcome to the Atlassian Community! This is just the end user community. You need to open a support ticket with Atlassian: https://support.atlassian.com/contact/#/

Hi Giulia - Welcome to the Atlassian Community! How are you identifying the "teams"? However that is, you just add that designation to the filter for each board - each board would require it's own filter. 

Hi Myles, Yes, the way you have it implies to me that ALL of them are required to be attached. 

Awesome - glad it is working!