WEB-1028On JIRA website, bots do unmeaningful transitions
Bots sometimes change the issue's resolving status unmeaningfully, for instance from "OPEN" to "OPEN", and so on.
Linked Issues
NormalCreated Issue:
On JIRA website, bots do unmeaningful transitions
Bots sometimes change the issue's resolving status unmeaningfully, for instance from "OPEN" to "OPEN", and so on.
Attachments2
Changed Description:
Bots sometimes change the issue's resolving status unmeaningfully, for instance from "OPEN" to "OPEN", and so on.
Bots sometimes change the issue's resolving status unmeaningfully, for instance from "OPEN" to "OPEN", and so on.
It may look like a (useless) transition, but the bot modifies internal / hidden fields.
When you tell us the ticket number, we can find out in detail what the bot did there.
OK I believe you're right, thank you. But I still want to satisfy my curiosity by asking, for example, what did [Bot] Arisa do when making the transition in
MC-128994?To clarify, we define a "Update Issue" transition that doesn't change the state of an issue (but allows editing of additional fields; in particular, confirmation status). You can see this if you click "view workflow".
[Bot] Arisa is actually open-source. What you're seeing is it updating the CHK field, which is the date at which an issue was confirmed; it sees when an issue's confirmation status is first set and sets the CHK field to that (relevant code).
Now, one thing that's a bit silly is that looking from feeds, JIRA will say "Arisa opened issue XXX" and the history only says "Open -> Open"; for some reason JIRA doesn't specify the actual transition name. They seem to have declared with as won't fix (JRASERVER-18528, JRASERVER-39904) though.
I see. Thanks very much!