John Funk Community Champion

Hi Lucas, I tend to go with what the customer wants. If there is a disagreement between some priorities, when one will make the customer happier to get first? Which will have the biggest impact for the customer? 

Great! Yeah, the Sub-tasks branch would not work if you are starting with a sub-task. It can only be used if the trigger issue is the parent of the sub-task. Anyway, enjoy the weekend!

Great! Glad it is working. But I think the key is that you took out the word parent from the one. I would still move that one above the child one - it should still work that way. 

Premium subscription will do it. 

So you are changing the value for a parent issue. That parent issue has sub-tasks and some of those subtasks have the same value for the date field. Correct so far? Are the Fri Date and Go Live Date fields the same types of fields (both date fields and one does not include Time? You might also try removing .fields. - you…

Looking forward to the Launch Readiness event. 

Nice use of the Confluence integration! Great article!

So that will need to be a second rule. Create that based on Field Value Changed. Then add a Branch for Linked Issues - identify the link type(s) if needed. Then add an action for Edit Issue, select the field and then say copy from Trigger issue. 

Hola, Marlene. ¡Bienvenida a la Comunidad de Atlassian! Como administrador de Jira, vaya a Configuración > Sistema > Funciones del proyecto. Luego haga clic en Administrar miembros predeterminados para los roles que tienen personas en ellos cuando se crea el proyecto y elimínelos.

Good - so what is missing now? 

Also, try taking the word parent out of the first condition (but leave child in the second one).

Hmmm, try just the one I posted further up for the Child value and see what it gives you. (You can just move the parent one below the child condition for now if you like - no need to delete it - just curious if that one passes). 

So can you share the rule where you are tying to update one issue based on the connected issue?

Yeah, I don't ever really remember creating a project based on an existing project that it would duplicate the board of the original project because Boards are not "shared" objects. So, if you create the project based on an existing project, what is "missing"? Other than the board that is. :-)

You need to add an action to the end of that for Link Issues and link the created issue to the trigger issue. 

Hmm, I am wondering if it is creating a new issue every time someone responds to the email. Are comments getting added to the original issue? For example, someone sends and email and the issue gets created. Then maybe they get an email that says, Hey! Thanks for creating an issue, here's the link for it. And then if they…

Sure that is very easy - they should be able to just change it to the other person (assuming they know who that is). They will need to have the Assign Issues permission in the Permission Scheme if they don't have that already. 

I would not use projects for that, I would use Epics. Projects in Jira are really more in line with Teams or Products. Are you creating projects based on existing projects? Are all of them getting created from scratch? Are they Company-managed? Team-managed? Sorry for all of the questions but that will be good feedback for…

Progress - great! Ad the end, try adding another Branch for Sub-tasks. Then place an Advanced Compare Condition below that comparing {{issue.Date Field}} equals {{triggerIssue.Date Field}} where Date Field is the exact name of the date field you are using. 

Hi Tolga - if you would, please respond inside the thread so that readers can follow the conversation easier. You need to have a link between the two projects, then you can update from there. Please share any rule that you have so far. 

If you would, please respond in the thread so that users can follow the conversation easier. :-) So is it possible that the Reporter actually created the second issue? And do you know how the original issue is getting created? Is it directly by someone? Or the result of some type of automation or post function in a…

Hi Shanmuga, You must be a Jira Administrator to create new Company-managed projects. Others can create Team-managed projects, but only if a Jira Administrator has turned on that permission or assigned it to you. 

Project creation should be something that is fairly rarely done, and typically only through a handful of administrators. Regardless, there will hopefully be a cleaner process that will come. 

Try using equals or contains instead of "contains regular expression". Then run again and post what the result is in the audit log.

HI @Eva Tsalkitzi My first question is why are you creating a new task every time it is assigned to a new person? That's a lot of extra work and issues that flood the system. Why can't the issue simply be reassigned to the next person and they continue working on the same issue as it moves through your workflow? 

Hi Gordon, Can you share the automation rule that you have so far? And where it is failing for you? 

Yes, you will definitely need to ask Atlassian to add that capability. I don't see any reason why would not/should not be able to use the queue if it can easily be identified. But that will be up to Atlassian to determine. Great suggestion!

You are very welcome. Let us know how it works out. 

You can then setup a Subscription for the filter to email you one a day or more often if you like. Or include it in a Dashboard

Use issueType = 'Einen Wartungsvorgang melden' and created >= startOfWeek() and statusCategory != Done