Discussion:
fossil humor: poor man's bug tracking...
(too old to reply)
Stephan Beal
2014-03-17 16:21:04 UTC
Permalink
For those who don't need the full features of the ticketing system, i think
i've discovered a new way to keep track of bugs: use a "fixme" tag.

[***@host:~/cvs/fossil/libfossil]$ f-tag -a 4b05c2c59fa6 -t fixme -v
"This artifact causes an HTTP 500 in the /manifest page of the CGI demo. It
is a 'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it)."

Applied tag [+fixme] to [4b05c2c59fa6]. New tag rid=4897 with value [This
artifact causes an HTTP 500 in the /manifest page of the CGI demo. It is a
'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it).] for user [stephan].

[***@host:~/cvs/fossil/libfossil]$ f push
Push to http://***@fossil.wanderinghorse.net/repos/libfossil/index.cgi
Round-trips: 1 Artifacts sent: 1 received: 0
Push finished with 1909 bytes sent, 2999 bytes received
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
j. van den hoff
2014-03-17 16:52:27 UTC
Permalink
Post by Stephan Beal
For those who don't need the full features of the ticketing system, i think
i've discovered a new way to keep track of bugs: use a "fixme" tag.
"This artifact causes an HTTP 500 in the /manifest page of the CGI demo. It
is a 'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it)."
Applied tag [+fixme] to [4b05c2c59fa6]. New tag rid=4897 with value [This
artifact causes an HTTP 500 in the /manifest page of the CGI demo. It is a
'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it).] for user [stephan].
Push to
Round-trips: 1 Artifacts sent: 1 received: 0
Push finished with 1909 bytes sent, 2999 bytes received
nice. but unfortunately not quite what we need here (it'd be somewhat
awkward to assign a jpeg image as the vaulue to the tag, e.g. ;-)).

what do other people think: is someone else missing the ability to
edit/modify ticket comments retrospectively?
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
Matt Welland
2014-03-17 16:56:06 UTC
Permalink
On Mon, Mar 17, 2014 at 9:52 AM, j. van den hoff
Post by Stephan Beal
For those who don't need the full features of the ticketing system, i
Post by Stephan Beal
think
i've discovered a new way to keep track of bugs: use a "fixme" tag.
"This artifact causes an HTTP 500 in the /manifest page of the CGI demo. It
is a 'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it)."
Applied tag [+fixme] to [4b05c2c59fa6]. New tag rid=4897 with value [This
artifact causes an HTTP 500 in the /manifest page of the CGI demo. It is a
'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it).] for user [stephan].
libfossil/index.cgi
Round-trips: 1 Artifacts sent: 1 received: 0
Push finished with 1909 bytes sent, 2999 bytes received
nice. but unfortunately not quite what we need here (it'd be somewhat
awkward to assign a jpeg image as the vaulue to the tag, e.g. ;-)).
what do other people think: is someone else missing the ability to
edit/modify ticket comments retrospectively?
I would put it at a "very strongly desired" level. I've needed the ability
to clean up mistakes a number of times and it is distracting to have
irrelevant junk in the history of a ticket.
Post by Stephan Beal
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Matt
-=-
90% of the nations wealth is held by 2% of the people. Bummer to be in the
majority...
JR
2014-03-17 16:56:40 UTC
Permalink
I miss it as well, but I am a one-man show on my repos, so it is more of an
inconvenience than anything. I would love to have the ability to edit the
initial comment field, though. I have a bunch of tickets I was testing with
and like to clean up.

JR
Post by Stephan Beal
For those who don't need the full features of the ticketing system, i
Post by Stephan Beal
think
i've discovered a new way to keep track of bugs: use a "fixme" tag.
"This artifact causes an HTTP 500 in the /manifest page of the CGI demo. It
is a 'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it)."
Applied tag [+fixme] to [4b05c2c59fa6]. New tag rid=4897 with value [This
artifact causes an HTTP 500 in the /manifest page of the CGI demo. It is a
'bad' artifact - accidentally imported from the fossil(1) repo during
manifest parsing tests. Should not crash, though (and the f-xxxx CLI tools
fail gracefully with it).] for user [stephan].
libfossil/index.cgi
Round-trips: 1 Artifacts sent: 1 received: 0
Push finished with 1909 bytes sent, 2999 bytes received
nice. but unfortunately not quite what we need here (it'd be somewhat
awkward to assign a jpeg image as the vaulue to the tag, e.g. ;-)).
what do other people think: is someone else missing the ability to
edit/modify ticket comments retrospectively?
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Stephan Beal
2014-03-17 17:00:37 UTC
Permalink
On Mon, Mar 17, 2014 at 5:52 PM, j. van den hoff
Post by j. van den hoff
nice. but unfortunately not quite what we need here (it'd be somewhat
awkward to assign a jpeg image as the vaulue to the tag, e.g. ;-)).
Yeah, it's ugly and limited, but that particular fixme has a very low
priority (i accidentally imported a foreign manifest into libfossil during
testing, and the CGI demo apps don't like that particular manifest).
Post by j. van den hoff
what do other people think: is someone else missing the ability to
edit/modify ticket comments retrospectively?
Fossil generally only shows the latest copy of a tag with a given name on a
given artifact, so if you tag it again with "fixme" you'd essentially
overwrite the original tag (insofar as fossil really overwrites anything).

Obviously not a general-purpose solution, it just came up spontaneously
when i didn't have emacs open to add the FIXME directly to some source code
;). i need to extend f-tag so that we can add multiple tags at a time, e.g.
fixme + bgcolor=pink :).
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
Stephan Beal
2014-03-17 20:30:37 UTC
Permalink
Post by Stephan Beal
Obviously not a general-purpose solution, it just came up spontaneously
when i didn't have emacs open to add the FIXME directly to some source code
;). i need to extend f-tag so that we can add multiple tags at a time, e.g.
fixme + bgcolor=pink :).
As if i don't have better things to do ;)

http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/manifest/1518b90df3e107babe829ee3cc6b1e0eff96ca70

Sample usage:

f-tag -a current -t addTag1 -v value1 -t -cancelTag2 -v value2 ...
--verbose --dry-run

@Jan: this is for you:

http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/info/7249b2eb8fe021d8
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
Ron Wilson
2014-03-17 18:35:26 UTC
Permalink
Post by j. van den hoff
nice. but unfortunately not quite what we need here (it'd be somewhat
awkward to assign a jpeg image as the vaulue to the tag, e.g. ;-)).
what do other people think: is someone else missing the ability to
edit/modify ticket comments retrospectively?
In another thread, I mentioned the possibility of using Javascript to
"replace" the ticket comment field with a Fossil wiki page. the result
would likely be kind of ugly, but would still have all the features
provided by Fossil tickets.

Another possibility, if one is willing/able to give up all the
ticket-specific features, would be to simply use wiki pages as the tickets.

(Honestly, the biggest obstacle to using any ticket system where I work was
the project managers *love* spreadsheets. Fortunately, "fossil ticket show"
produces a tab separated listing based on the specified report. Except
during meetings, they update tickets through the web interface. During
meetings, they still just make the changes in the spreadsheet, I have to
export the updated spreadsheet to a CSV file and use a Perl program to
generate "fossil ticket change" commands.)
Continue reading on narkive:
Loading...