Below is the history record for the change of the issue security level.
Can anyone help to understand what the actual change was?
What was the original value / setting of the issue security?
And how this information is supposed to be useful?
Thank you.
Hi @Inna S ,
as @John Funk said it seems that Security Level has been cleared. Btw I have two question :
Fabio
Hi Inna,
It says that you cleared out the issue security level for the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk this long string is supposed to convey some information, that I'm unable to decipher.
I do see the name of the field that was altered and I see that it was cleared.
But this long string is there for a reason, I guess and I do not understand it.
Again, the history record is supposed to state the 'before' and 'after' values of the 'field', the 'timestamp' and the actor. One of these is missing.
Within the wider context of the buggy history records, e.g. re Fix Version, I suspect something is very wrong and unreliable with it.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, I think it includes all four of those things from what I see. The timestamp is clearly there, and you are the actor. The long string is the value before and the word Nunn is the value after, which means the value before was cleared.
The Longstream appears to be the ID of the security level. Since it’s security related, that’s probably why it’s just an ID and not a name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk , apologies for the delayed reply: apparently I've got banned from posting for answering too many comments in a short period of time.
On the matter:
The encrypted security level does not convey the useful information.
I need to know what was the original / next value, like 'visible to admins only'.
How does this hash help anyone to understand what happened there?
Also, there is no history search for Security Level 'field'.
We are missing the usable audit of the security related event.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can navigate to one of the security levels that you have on the project. Go to Settings > Issues > Issue Security Schemes.
Then search for your scheme. Next click on the Security Levels link on the far right.
If you have multiple security levels, click on one of them.
Then look at the URL for the security level to see the token.
You can copy the token from the history entry and paste it into the URL to see which one was cleared.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, @John Funk . Is this documented somewhere? I have not seen it.
Very original way to convey critical information nevertheless.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, @John Funk , the team managed projects do not have the Issue Security Schemes. Or at least I could not find one following the Settings -> Issues path.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I doubt it - Atlassian documentation leaves much to be desired. Honestly, I had not seen that before for security levels either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, there are a couple of open feature requests to add Issue Security to Team-managed projects, but I have seen no movement on those.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As discussed in the other, old thread,
We found the Issue Security Schemes do exist for Team Managed projects, but they are not modifiable and they are not documented.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.