How to set up a template for recurring tasks?

[Kerrie Zeng]

How to set up a template for recurring tasks?

[Tuncay Senturk _Snapbytes_ · Accepted solution]

As far as I know, it is by design.

You can not change updated field unless you do some hack (modifying the db value).

[Derek Fields _RightStar_]

What is the point of setUpdated () if it doesn't do anything?

[Tuncay Senturk _Snapbytes_]

You're right from this point of view, and you're not alone.

Here you can see similar conversation and a workaround. Thay may help.

Or, could you try adding below statement after updating MutableIssue? (I am not sure, but it may work I guess)

issue.store()

[Derek Fields _RightStar_]

Using issue.store() instead of IssueManager.updateIsssue worked - which is frustrating. It is also risky as a long-term solution, since store() is deprecated. The good news is that I should only have to use it for a short term fix. 

I also determined that it is possible to do a direct database update into the jiraissue table, so that it a less risky workaround since that table structure is stable.

Thanks for the help

[Tuncay Senturk _Snapbytes_]

Glad to hear that