Re: [fossil-users] ticket that depends on another ticket
Sorry, forgot to add that for the code to work you need also to add field:
blockers TEXT, to the ticket table (Admin/Tickets/Common).
Cheers,
Jacek
2014-10-01 6:26 GMT+01:00 Jacek Cała :
> Hi Paolo,
>
> Below are things which I use, based on various answers from the mailing
> list. Have a look at these excerpts and put them in the appropriate places
> via Admin/Tickets/Edit or View
>
> Basically, I changed the edit and view ticket pages to add/show blockers.
> As said above, it's just for informative purposes, so e.g. you will be able
> to close ticket with unclosed blockers. But I use it and still find it
> handy. BTW, in the view page I use colors to clearly show ticket status,
> without proper support from fossil I don't think you can show that a ticket
> is blocked by others.
>
> Hope it helps,
> Jacek
>
> - Edit ticket page -
>
> if {![info exists mutype]} {set mutype Wiki}
> if {![info exists icomment]} {set icomment {}}
> if {![info exists username]} {set username $login}
> if {[info exists submit]} {
> if {$mutype eq "Wiki"} {
> set mimetype text/x-fossil-wiki
> } elseif {$mutype eq "HTML"} {
> set mimetype text/html
> } elseif {$mutype eq {[links only]}} {
> set mimetype text/x-fossil-plain
> } else {
> set mimetype text/plain
> }
>
> # Set blockers according to the buffered new_blockers list
> set blockers $new_blockers
>
> submit_ticket
> set preview 1
> }
>
>
> ...
>
> Version Found In:
>
>
>
>
> Blockers:
>
> if {! [info exists new_blockers]} {
> set new_blockers $blockers
> }
>
> if {[info exists addblckrbtn]} {
> if {[info exists new_blocker]} {
> # Check whether the added blocker is already in the list
> set add_new_blocker 1
> for {set b 0} {$b < [llength $new_blockers]} {set b [expr {$b + 1}]}
> {
> set to_check [lindex $new_blockers $b]
> if {![string compare $new_blocker $to_check]} {
> set add_new_blocker 0
> break
> }
> }
> if {$add_new_blocker} {
> set new_blockers "$new_blockers $new_blocker"
> }
> }
> } elseif {[info exists delblckrbtn]} {
> if {[info exists blocker_list]} {
> # Generate a list of blockers that is clear from the deleted blocker
> set cleared_blockers ""
> for {set b 0} {$b < [llength $new_blockers]} {set b [expr {$b + 1}]}
> {
> set to_check [lindex $new_blockers $b]
> if {[string compare $blocker_list $to_check]} {
> set cleared_blockers "$cleared_blockers $to_check"
> }
> }
> set new_blockers $cleared_blockers
> }
> }
>
> html ""
> if {[llength $new_blockers] == 0} {
> enable_output 0
> }
>
> combobox blocker_list "$new_blockers" 3
>
>
>
>
>
> enable_output 1
>
>
>
>
>
> Append Remark with format
>
> ...
> - End of Edit Ticket page -
>
> - View Ticket page -
> ...
>
>
> Title:
> $
>
>
> Status:
>
> if {![string compare $status "Verified"] ||
> ![string compare $status "Open"]} {
> set color "#ff"
> } elseif {![string compare $status "Review"]} {
> set color "#e8e8e8"
> } elseif {![string compare $status "Fixed"]} {
> set color "#cfffbd"
> } elseif {![string compare $status "Tested"]} {
> set color "#bdffd6"
> } elseif {![string compare $status "Deferred"]} {
> set color "#aabaff"
> } else {
> set color "#b8b8b8"
> }
> html "$status"
>
> Type:
>
> ...
>
>
> Version Found In:
> $
> Assigned to:
> $
>
>
> Blockers:
>
>
># Thanks to Brian Theado
>#
> http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg00852.html
>
># Loop through the ticket uuids
>for {set x 0} {$x < [llength $blockers]} {set x [expr {$x + 1}]} {
> # Add braces so wiki formatter will make links. Backslashes
> # hide those braces from interpretation by th1
> wiki \[[lindex $blockers $x]\]
>}
>
>
>
>
>
> if {[info exists comment] && [string length $comment]>10} {
> html {
> Description:
>
> }
>
> ...
>
> - End of View Ticket page
>
>
> 2014-09-30 20:17 GMT+01:00 Ron W :
>
>> On Tue, Sep 30, 2014 at 2:17 PM, Stephan Beal
>> wrote:
>>
>>> On Tue, Sep 30, 2014 at 6:43 PM, Paolo Bolzoni <
>>> paolo.bolzoni.br...@gmail.com> wrote:
>>>
I am using fossil for bug tracking in a project where (not my
decision) we use git for revision control. I was wondering if
there is a way to explicitly mark a ticket as children of
another. So it is clear that the root one must worked on before
the child one.
It is possible do something like that?
>>>
>>> There's nothing at the infrastructure-level which directly supports
>>> that, but you could add a custom field which holds a list of other ticket
>>> IDs. Fossil would apply no special logic to it, though, e.g. "can't do a
>>> release so long as
Re: [fossil-users] ticket that depends on another ticket
Hi Paolo,
Below are things which I use, based on various answers from the mailing
list. Have a look at these excerpts and put them in the appropriate places
via Admin/Tickets/Edit or View
Basically, I changed the edit and view ticket pages to add/show blockers.
As said above, it's just for informative purposes, so e.g. you will be able
to close ticket with unclosed blockers. But I use it and still find it
handy. BTW, in the view page I use colors to clearly show ticket status,
without proper support from fossil I don't think you can show that a ticket
is blocked by others.
Hope it helps,
Jacek
- Edit ticket page -
if {![info exists mutype]} {set mutype Wiki}
if {![info exists icomment]} {set icomment {}}
if {![info exists username]} {set username $login}
if {[info exists submit]} {
if {$mutype eq "Wiki"} {
set mimetype text/x-fossil-wiki
} elseif {$mutype eq "HTML"} {
set mimetype text/html
} elseif {$mutype eq {[links only]}} {
set mimetype text/x-fossil-plain
} else {
set mimetype text/plain
}
# Set blockers according to the buffered new_blockers list
set blockers $new_blockers
submit_ticket
set preview 1
}
...
Version Found In:
Blockers:
if {! [info exists new_blockers]} {
set new_blockers $blockers
}
if {[info exists addblckrbtn]} {
if {[info exists new_blocker]} {
# Check whether the added blocker is already in the list
set add_new_blocker 1
for {set b 0} {$b < [llength $new_blockers]} {set b [expr {$b + 1}]} {
set to_check [lindex $new_blockers $b]
if {![string compare $new_blocker $to_check]} {
set add_new_blocker 0
break
}
}
if {$add_new_blocker} {
set new_blockers "$new_blockers $new_blocker"
}
}
} elseif {[info exists delblckrbtn]} {
if {[info exists blocker_list]} {
# Generate a list of blockers that is clear from the deleted blocker
set cleared_blockers ""
for {set b 0} {$b < [llength $new_blockers]} {set b [expr {$b + 1}]} {
set to_check [lindex $new_blockers $b]
if {[string compare $blocker_list $to_check]} {
set cleared_blockers "$cleared_blockers $to_check"
}
}
set new_blockers $cleared_blockers
}
}
html ""
if {[llength $new_blockers] == 0} {
enable_output 0
}
combobox blocker_list "$new_blockers" 3
enable_output 1
Append Remark with format
...
- End of Edit Ticket page -
- View Ticket page -
...
Title:
$
Status:
if {![string compare $status "Verified"] ||
![string compare $status "Open"]} {
set color "#ff"
} elseif {![string compare $status "Review"]} {
set color "#e8e8e8"
} elseif {![string compare $status "Fixed"]} {
set color "#cfffbd"
} elseif {![string compare $status "Tested"]} {
set color "#bdffd6"
} elseif {![string compare $status "Deferred"]} {
set color "#aabaff"
} else {
set color "#b8b8b8"
}
html "$status"
Type:
...
Version Found In:
$
Assigned to:
$
Blockers:
# Thanks to Brian Theado
#
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg00852.html
# Loop through the ticket uuids
for {set x 0} {$x < [llength $blockers]} {set x [expr {$x + 1}]} {
# Add braces so wiki formatter will make links. Backslashes
# hide those braces from interpretation by th1
wiki \[[lindex $blockers $x]\]
}
if {[info exists comment] && [string length $comment]>10} {
html {
Description:
}
...
- End of View Ticket page
2014-09-30 20:17 GMT+01:00 Ron W :
> On Tue, Sep 30, 2014 at 2:17 PM, Stephan Beal
> wrote:
>
>> On Tue, Sep 30, 2014 at 6:43 PM, Paolo Bolzoni <
>> paolo.bolzoni.br...@gmail.com> wrote:
>>
>>> I am using fossil for bug tracking in a project where (not my
>>> decision) we use git for revision control. I was wondering if
>>> there is a way to explicitly mark a ticket as children of
>>> another. So it is clear that the root one must worked on before
>>> the child one.
>>>
>>> It is possible do something like that?
>>>
>>
>> There's nothing at the infrastructure-level which directly supports that,
>> but you could add a custom field which holds a list of other ticket IDs.
>> Fossil would apply no special logic to it, though, e.g. "can't do a release
>> so long as this blocker ticket is opened."
>>
>
> Using TH1, it is possible to encode various ticket handling steps. A few
> years ago, I shared the custom TH1 code I wrote for my team. We don't use
> it anymore. If I can find a copy, I'll post it, again. Or it should be
> somewhere in the archive of this mailing list (I haven't posted a ton of
> messages so it shouldn't be very hard to find.)
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:80
Re: [fossil-users] ticket that depends on another ticket
On Tue, Sep 30, 2014 at 2:17 PM, Stephan Beal wrote: > On Tue, Sep 30, 2014 at 6:43 PM, Paolo Bolzoni < > paolo.bolzoni.br...@gmail.com> wrote: > >> I am using fossil for bug tracking in a project where (not my >> decision) we use git for revision control. I was wondering if >> there is a way to explicitly mark a ticket as children of >> another. So it is clear that the root one must worked on before >> the child one. >> >> It is possible do something like that? >> > > There's nothing at the infrastructure-level which directly supports that, > but you could add a custom field which holds a list of other ticket IDs. > Fossil would apply no special logic to it, though, e.g. "can't do a release > so long as this blocker ticket is opened." > Using TH1, it is possible to encode various ticket handling steps. A few years ago, I shared the custom TH1 code I wrote for my team. We don't use it anymore. If I can find a copy, I'll post it, again. Or it should be somewhere in the archive of this mailing list (I haven't posted a ton of messages so it shouldn't be very hard to find.) ___ 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] ticket that depends on another ticket
On Tue, Sep 30, 2014 at 6:43 PM, Paolo Bolzoni < paolo.bolzoni.br...@gmail.com> wrote: > I am using fossil for bug tracking in a project where (not my > decision) we use git for revision control. I was wondering if > there is a way to explicitly mark a ticket as children of > another. So it is clear that the root one must worked on before > the child one. > > It is possible do something like that? > There's nothing at the infrastructure-level which directly supports that, but you could add a custom field which holds a list of other ticket IDs. Fossil would apply no special logic to it, though, e.g. "can't do a release so long as this blocker ticket is opened." -- - 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] ticket that depends on another ticket
Dear list, I am using fossil for bug tracking in a project where (not my decision) we use git for revision control. I was wondering if there is a way to explicitly mark a ticket as children of another. So it is clear that the root one must worked on before the child one. It is possible do something like that? Cheers, Paolo ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
