update field from epic to tasks in JMWE

[Diallo]

Hello everyone, i have an issue about updating the fields in my tasks when this field have modified in its parent(epics). i use JMWE even base action

so for the rule it like that :

When : issue field value changed (to select the all field with concern)

if scope : any project, issuetype (epic)

then copy issue field

with this The value(s) of the following fields will be copied from the current issue to each issue that belongs to the current Epic about link.

but there is not update in the in the task when i modified this field in epic, in the log, it just  return None without error.

[Marc -Devoteam-]

Hi @Diallo 

Are you using JWME for this or an automation rule, can you provide more context and show screenshots of this configuration and where this is placed?

[Diallo]

Yes, I was using JMWE as usual, everything was going well, but currently, a lot of automation in JWE is not working, I don’t know why, I haven’t had any errors in anything. but it does'nt not work.

---

i tested the link issue that belong to current issue (epic), child issue of the current issue..... but none of is work, no error but child ticket received N/A

[Marc -Devoteam-]

Hi @Diallo 

Are the fields avaialbe on the screen used by the child items of the Epic or are there field context in play that prevent this?

[Diallo]

yes, and whe checked the troubleshooting and support for jmwe i had, We have detected errors in your logs that indicate a probable issue with some Permission Schemes and/or some Issue Security Schemes : but the all permission and scurity sheme is ok

[Marc -Devoteam-]

Hi @Diallo 

What have you setup in JWME, an event?

Is the event set in a post function of the workflow?

Also you mention support from the app vendor, lead to permission issues, is the executing user part of the space, does the event span multiple spaces?

Rather other question, why not use an automation rule for this?

[Diallo]

yes it is an even in JMWE

yes it's me who executes it and i'm an administrator

now i use it, but i want to know why the rule in jmwe does'nt work whereas it works well before

[Marc -Devoteam-]

Hi @Diallo 

Is the even triggered in the post function of the transition, and which user is the actor?

Does this actor have a JSM license and is member of the Service Desk Team role in the JSM space?

[Diallo]

I used the JMWE plugin, not JSM. It has these rules as an image, so no errors or warnings. With this JQL, when tested with epics, it greatly returns all the epics children, but the update is not done in the child fields. In the logs, I have N/A; the same thing happens if I do it in native Jira, so I don’t understand.

For the experiment, I added an add-on user, and that’s me testing it

[Marc -Devoteam-]

Hi @Diallo 

The scope of the JQL seems to be off: parent = {{issue.key}}

Where is this smart variable defined?

As I seen this now it will look if the Epic this event actions on need to have a parent field set.

If you want Epic children to be affected, the scope most be on issue types below Epic.

Is there an option to check in the event what issues are found?

[Diallo]

@marc ,  Normally, it’s an entry log but; but I only have N/A, I tried a lot of links for access, but I only get N/A, as shown in the images.

[Marc -Devoteam-]

Hi @Diallo 

I have made a similar setup on my side and this worked, the logs also show N/A but the action is down on the related issues

Are you pinpointing the right Issue Type, as Epic needs to be chosen (not an Epic in a Team Managed space, as they are specified individually)

[Diallo]

on my end, it's doesn't work, maybe the issue is elsewhere not on th rules, thanks for your assistance