Hi,
I have a question about the Jira Align API for Risks (/align/api/2/Risks/{id}), because for about a month when we create a new risk, the lastUpdatedDate is set to good date, but timestamps are always at 00:00:00 no matter what time we add a risk.
So basically, if I create a risk on 01/25/2024 at 4:36:13 PM, I see "createDate": "2024-01-25T16:36:13Z" which is correct, but "lastUpdatedDate": " 2024- 01-25T00:00:00Z"
...Is this normal? I don't remember it being handled like that before.
This phenomenon happens when we create a new risk, but when a risk is updated, the lastUpdatedDate is correct.
Regards,
Viviane
@WU Viviane is this still happening? i just ran a test and see a timestamp for lastUpdatedDate:
Yes, it happens when a risk is created, but when the risk is updated it's good
I just retested, I created a new risk ans this is what I got:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But if I modify the risk, therefore there is an update, then it's good I have:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Strange! if not having the timestamp on the create is an issue for you, then i'd suggest you open a support ticket for someone to investigate further.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Stand out as a skilled Confluence Cloud administrator. The Confluence Administration for Cloud certification proves you can configure permissions, manage site and space settings, and monitor activity—ensuring secure, effective collaboration for your team.
Start here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.