Unable to match IssueType=Epic criteria when moving from a non-Epic to Epic

[Derrick Lim]

Hi everyone, I have been stumped over this for a while now.

I have created an automation such that when a new Issue is created and it matches an "Epic" and other criteria, a set of sub tasks will be created. The key trigger is when an issue is created.

Now, my aim is to extend this automation to when I am moving from a regular task to an epic. Initially, I changed the trigger to be multiple triggers consisting of (Issue Created and Issue moved)

Problem - This automation would not trigger when I moved an issue type from task to epic.

After some trial and error, I tested that when a task is moved to an epic, I managed to trigger "Issue created" but not "Issue moved". I tried with the multiple issues trigger and also the standalone "Issue moved" with the project being any project > project A as well as Project A to Project A. None of which triggered.

Anyone able to resolve how I can correctly trigger a automation when a issue type (Task) is moved to an (Epic)?

You can see here the current issue type = Task and I have another criteria where a field Partner Type = Payin value (I have also tested with removing this Partner type criteria and it doesn't change anything. So my suspicion is that the condition Issue type = Epic is not being triggered)

Used "Move" to change the issue type from a "task" to an "Epic"

After the issue has been moved and updated an an Epic.

Audit log shows that the criteria was not met, as mentioned above, I have tested leaving only "Issue type equals Epic" or "Issue type is one of Epic" and it will still fail the criteria.

[tnewton1 · Accepted solution]

Alright - so here's how I solved this. I setup Jira as a fresh install. Once I got logged in, I attempted an import using the zip I created when I backed this up. When I imported from the fresh install, I got an error that was actually helpful. A comment had a smiley in it (☺) and I had to go into the activeobjects.xml in Notepad++, delete it, re-zip the files, then importing it and it successfully uploaded. I don't know if this is a bug, but it might be. Seems a little strange I got an error completely un-related until I did a fresh install of Jira. Thanks for getting me on the right path though!

[Andy Heinzer]

ah,  Thanks for clarifying.  It's a known limitation that mysql databases cannot store 4-byte characters.  Hence characters like emojis can't be stored in those databases.   This is something that looks like it might get fixed in the next major version of Jira per https://jira.atlassian.com/browse/JRASERVER-36135

[Andy Heinzer]

Two things I would check:

1. Windows systems have a tendency to default themselves to hide file extensions.  If this is enabled in your system, then the file might actually have a filename such as MigrateToMySQL.zip.zip  In which case you need to enter it exactly as such to get Jira to use this.   You could confirm the true filename by going to a command prompt in this directory (cmd.exe) and the doing a dir command to see the actual filename.
2. If that is not the case, please extract this file to make sure that it has exactly two files in it:  activeobjects.xml and entities.xml.  You won't be able to import just the xml files directly, they do need to be inside a zip file for this to work.

[tnewton1]

Yep, it only has one extension. Extracted it and the two files activeobjects.xml and entities.xml are in there.

When I import the zip file, I see it go to a screen where it looks like it's extracting the files. But I've seen it disappear after a random percentage (could be 20%, could be 2% - it varies each time I do this).

I'm starting to get behind on work. Could I just setup Jira as a fresh install and then restore from the latest automated backup zips?

[Alexey Matveev]

Hello,

You should not unzip the MigrateToMySQL.zip file. Just write MigrateToMySQL.zip during import.

[tnewton1]

Did that. Still get “You must enter the location of an XML file.”