You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/09/11 18:22:02 UTC
[Apache Bloodhound] #199: Changes in ticket fields reverted on
concurrent modifications
#199: Changes in ticket fields reverted on concurrent modifications
--------------------------------------------+--------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: trac core | Version:
Keywords: ticket view fields concurrency |
--------------------------------------------+--------------------
The following sequence of events may result in modifications reverted .
That's annoying
|| User || Action || Observations ||
|| A || opens ticket page || ||
|| B || modifies ticket field || ||
|| A || adds a new comment || while writing the text , comments feed is
updated and warning message about concurrent modifications is displayed ,
nonetheless latest values for ticket field are not updated ||
As a consequence changes to ticket fields may be reverted .
We shall review whether this should improved or just close this ticket as
wontfix and be more careful.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/199>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #199: Changes in ticket fields reverted on
concurrent modifications
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#199: Changes in ticket fields reverted on concurrent modifications
--------------------------+--------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: trac core | Version:
Resolution: | Keywords: ticket view fields concurrency
--------------------------+--------------------------------------------
Description changed by olemis:
Old description:
> The following sequence of events may result in modifications reverted .
> That's annoying
>
> || User || Action || Observations ||
> || A || opens ticket page || ||
> || B || modifies ticket field || ||
> || A || adds a new comment || while writing the text , comments feed is
> updated and warning message about concurrent modifications is displayed ,
> nonetheless latest values for ticket field are not updated ||
>
> As a consequence changes to ticket fields may be reverted .
>
> We shall review whether this should improved or just close this ticket as
> wontfix and be more careful.
New description:
The following sequence of events may result in modifications reverted .
That's annoying
|| User || Action || Observations ||
|| A || opens ticket page || ||
|| B || modifies ticket field || ||
|| A || adds a new comment || while writing the text , comments feed is
updated and warning message about concurrent modifications is displayed ,
nonetheless latest values for ticket field are not updated ||
As a consequence (as already happened in comment:ticket:67:16 ) changes to
ticket fields may be reverted .
We shall review whether this should improved or just close this ticket as
''wontfix'' and be more careful.
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/199#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #199: Changes in ticket fields reverted on
concurrent modifications
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#199: Changes in ticket fields reverted on concurrent modifications
--------------------------+--------------------------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: trac core | Version:
Resolution: | Keywords: ticket view fields concurrency
--------------------------+--------------------------------------------
Comment (by jdreimann):
So does B just have to enter edit state, or does B have to submit an edit
before A is shown the concurrent modification message?
If B submits first, I reckon we should push the changes B makes to A's
ticket page immediately, displaying the change event in the Activity feed
and updating the highlighted field.
If A is also in an edit state and is editing the same filed (let's say B
changed the milestone and A is about to do the same) it should be okay for
A to lose the changes made, as long as it's clear to the user that it
happened because B submitted a change. (Highlighted field and activity
feed entry should do the job)
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/199#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker