[fossil-users] unexpected ticket behavior
I tried to reassign a ticket and append a comment at the same time. (I have an assigned-to field. I'm not sure if I added that or if it's standard.) My changes silently failed--I just ended up viewing the unchanged ticket. After trying this several times, downloading the latest snapshot, and rebuilding my repos to no avail, I eventually did it in two separate steps, and it worked. This is contrary to what I would expect and how other systems work. (E.g., used to be in bugzilla that you couldn't make any other changes unless you added a comment at the same time!) If there's a good reason for having it this way, it definitely should let me know why it's ignoring my changes. (If the reason is to make a clearer history trail, I'd rather fossil just generated two history events from my two-changes-in-one submission.) -- Joshua Paine LetterBlock: Web applications built with joy http://letterblock.com/ 301-576-1920 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] unexpected ticket behavior
Refer to the fossil ticketing system ticket id: 3dbc12f49d on 4 April 2010. On Mon, 2010-04-19 at 06:16 -0400, Joshua Paine wrote: I tried to reassign a ticket and append a comment at the same time. (I have an assigned-to field. I'm not sure if I added that or if it's standard.) My changes silently failed--I just ended up viewing the unchanged ticket. After trying this several times, downloading the latest snapshot, and rebuilding my repos to no avail, I eventually did it in two separate steps, and it worked. This is contrary to what I would expect and how other systems work. (E.g., used to be in bugzilla that you couldn't make any other changes unless you added a comment at the same time!) If there's a good reason for having it this way, it definitely should let me know why it's ignoring my changes. (If the reason is to make a clearer history trail, I'd rather fossil just generated two history events from my two-changes-in-one submission.) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] unexpected ticket behavior
On Mon, Apr 19, 2010 at 12:16 PM, Joshua Paine jos...@letterblock.comwrote: I tried to reassign a ticket and append a comment at the same time. (I have an assigned-to field. I'm not sure if I added that or if it's standard.) My changes silently failed--I just ended up viewing the unchanged ticket. After trying this several times, downloading the latest snapshot, and rebuilding my repos to no avail, I eventually did it in two separate steps, and it worked. i had a similar problem where i added a Subsystem field to the initial ticket view (it normally doesn't appear there). When setting the subsystem via the ticket-open view the setting never stuck. When subsequently editing the ticket later, it did stick. My assumption is that the ticket-posting code is different for an initial ticket, and only accepts a hard-coded list of fields, but i didn't look into it (i was just happy to have a workaround). -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
