Dear @Jeffrey Canales,
don't get you - some more warm words could help.
Thanks
Thomas
Which "time stamp update"? Where are you looking? Is there something wrong with the issue history?
Hi @Nic Brough -Adaptavist-
The users wants to record another date without overwriting the original date if the workflow is repeated.
I am guessing what you mean here is that you have a field that takes on the date/time of "now" when a specific transition happens. If the transition happens again, then it updates the field.
The problem here is that a field is a single object. There is nowhere to put the old date in that field, because it's a field that holds a single date.
So the simple answer is "no". However, that "write date" is not a native function in Jira, so it implies you have got some code that does it. I would look to alter that code so that it looks at the history and says "if this transition has been used before, do not write the date in".
Also, you should find that the change of field is written into the history - would that record be enough?
And if you had Script Runner, you could write a scripted field to pull the first date of transition from the history, then you wouldn't need this date field at all.
It looks like you're new here. Sign in or register to get started.
