Remote changes to sprint assignment doesn't create a version?
For some reason, it seems that if you do a remotely change the sprint for a given ticket (either changing it or unassigning it altogether), no version is created to reflect that change. Is this by design, or a bug? According to the documentation, "Every ticket update creates a new ticket version", but that doesn't seem to be the case here. Please advise. Thanks!
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by brandi on 28 Jan, 2013 08:43 PM
Hi Justin,
If I'm understanding your question correctly, you are expecting a new version of a ticket every time you update said ticket? You would not get a an identical, "new" ticket version showing each time a change is made, but you will receive notifications of change in the activity stream and/or the changes would show in the original ticket's activity, ie. "user has been changed to X, title has been changed to Y" would appear inside the ticket's history.
Let me know if this did not address your issue.
Thanks!
Brandi
2 Posted by Justin Bingham on 28 Jan, 2013 08:46 PM
Hi Brandi,
Not a new version of the ticket, but a new 'version' associated with the
ticket object (which would correlate to an entry in the ticket's activity
stream that you reference).
As it stands now, this isn't happening. Note that I'm talking about an
update through the API only. This isn't the case when using the web app.
Here's a list of steps to reproduce.
1. Create a ticket through the api
2. Change the ticket's sprint assignment through the api
You will note that there is no ticket version created to correspond with
this change, nor is there any record of it in the activity stream for the
ticket.
Thanks!
Support Staff 3 Posted by Tiger Team on 28 Jan, 2013 09:34 PM
Hey Justin,
Sorry, brandi didn't see the 'api' request! So-- what do you mean 'sprint assignment'? We don't use those words in LH anywhere, so wondering what your api call is.
4 Posted by Justin Bingham on 28 Jan, 2013 09:51 PM
ah no worries. i mean milestone. so by changing assignment i mean assigning a ticket to a milestone, or changing the milestone assignment from one to the other
Support Staff 5 Posted by Tiger Team on 28 Jan, 2013 10:44 PM
Oh, right.
I just checked here and we definitely add a new ticket version when you're changing milestone. We do, however, compress events that happen within a few minutes, so if you immediately change milestone it might not show up (it's an "oops" feature). Does this happen for you on old tickets too?
6 Posted by Justin Bingham on 28 Jan, 2013 10:47 PM
ahhhh. that makes sense. i actually just noticed this same behavior while experimenting with something else. now that i know that i can work around it. i've got some local versioning and my code was trying to assume that the remote version lined up exactly with the remote and was complaining, but the collapsing would explain it. i can work around that. thanks!
Julien closed this discussion on 29 Jan, 2013 07:07 PM.