Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with "Last Executer" Column

Daniel Caloto July 25, 2013

Hello.

We have updated the plugin JIRA Suite utilities to version 1.4.7. (JIRA 6.0.4)
In Issue view, on the "Transitions Summary" tab, column "Last Executer", we see:

#authorlinkname(${tran.lastUpdater})

What is wrong?

How can we resolve the error?

Thanks in advance

5 answers

1 accepted

0 votes
Answer accepted
Daniel Caloto September 18, 2013

Our problem was that we were using the macros.vm file for version 4.4.1. We have changed this file for version 6.0.4 and everything works fine.

You can locate this file in JIRA_INSTALL\...\WEB-INF\classes\templates\email

0 votes
Daniel Caloto September 17, 2013

We solved the problem. The error was in the file macros.vm.

Bruno
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 18, 2013

I have the some problem. Could you explain me please what was exactly the problem in macros.vm ?

Where is the location of macros.vm?

Ramiro Pointis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2013

In my case, since I don't have access to server I just downgraded to version 1.4.6

In that version it's working fine.

0 votes
Ramiro Pointis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 17, 2013

Did you resolve this? In case you did then how?

0 votes
Daniel Caloto July 28, 2013

I have performed a re-index and a restart the instance, and the error still occurs

0 votes
MJ
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 25, 2013

There has beena bug regarding the 1.4.6 version which has been documented here. Presumably you have updated from this version to 1.4.7.
Have you performed a re-index or maybe even a restart of the instance, and has that changed anything?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events