I have two email subject templates issuecreated.vm and issueresolved.vm that is exactly the same. However, issuecreated.vm works but not issueresolved as expected.
[raymond@smfc-aij-07-sr1 subject]$ ls -al issuecreated.vm issueresolved.vm -rw-r--r-- 1 atlassian atlassian 186 Jul 12 00:27 issuecreated.vm -rw-r--r-- 1 atlassian atlassian 186 Jul 12 00:27 issueresolved.vm [raymond@smfc-aij-07-sr1 subject]$ diff issuecreated.vm issueresolved.vm [raymond@smfc-aij-07-sr1 subject]$ cat issuecreated.vm #if ($issue.getCustomFieldValue("customfield_10044")) ($issue.key) $issue.getCustomFieldValue("customfield_10044"): $issue.summary #else ($issue.key) $issue.summary #end [raymond@smfc-aij-07-sr1 subject]$ cat issueresovled.vm cat: issueresovled.vm: No such file or directory [raymond@smfc-aij-07-sr1 subject]$ cat issueresolved.vm #if ($issue.getCustomFieldValue("customfield_10044")) ($issue.key) $issue.getCustomFieldValue("customfield_10044"): $issue.summary #else ($issue.key) $issue.summary #end [raymond@smfc-aij-07-sr1 subject]$
Here is the subject line output of a test issue, the "SEV3" is the customfield_10044
issue created:
Problem resovled! It is in my workflow transition post mortem functions, the last function was set to "Fire generic event" instead of "Fire Issue Resolved event"(See screen shot). Thus, "Issue Resolved" event was never fired, hence email subject template issueresolved.vm wasn't involved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.