On Mon, Oct 7, 2013 at 11:31 AM, Matt Welland wrote:
>
> Applying constraints as receiver end filtering could be very useful and I
> think it could fit the sync model if not needed blobs were not necessarily
> dropped but a record was kept so that they wouldn't be sync'd and they are
> kept out o
Applying constraints as receiver end filtering could be very useful and I
think it could fit the sync model if not needed blobs were not necessarily
dropped but a record was kept so that they wouldn't be sync'd and they are
kept out of the list of blobs. Essentially something similar to what the
sh
On Sun, Oct 6, 2013 at 9:55 PM, Joseph R. Justice wrote:
> During the push, it is noticed that R(N) says bug B2 is closed while R'
> says it is open and blocked by B1 (and that A specified the block), which
> is open both in R' and R(N). N should be notified of this as it is
> something which can
On Wed, Oct 2, 2013 at 10:22 AM, Stephan Beal wrote:
Ignoring the complication of having to parse/grok the content (it's a minor
> complication, granted, but parsing text is always at least a slight
> annoyance), there's another problem: DVCS. i edit the field, then you close
> the ticket in your
On Wed, Oct 2, 2013 at 10:47 AM, Stephan Beal wrote:
>
> Most just don't generate as much noise as i do, so you haven't seen them
> yet in your short time here ;).
>
Noise? I'd say you have a very high signal-to-noise ratio.
___
fossil-users mailing li
On Wed, Oct 2, 2013 at 10:31 AM, Jacek Cała wrote:
> in the field (possibly without commas, or a mixture). Ignoring the
>> complication of having to parse/grok the content (it's a minor
>> complication, granted, but parsing text is always at least a slight
>> annoyance), there's another problem:
On Wed, Oct 2, 2013 at 4:40 PM, Krister Johnson wrote:
> I just started using fossil. It is heartening to see there are so many
> people contributing.
>
Fossil has quite a few contributors:
http://www.fossil-scm.org/fossil/reports?view=byuser
Most just don't generate as much noise as i do, so
Jacek,
I just started using fossil. It is heartening to see there are so many
people contributing.
I haven't run into that need yet, but it doesn't mean i won't. Thanks for
putting this out there. I will know where to find it if that need arises.
Krister
On Wed, Oct 2, 2013 at 9:31 AM, Jacek C
>
> in the field (possibly without commas, or a mixture). Ignoring the
> complication of having to parse/grok the content (it's a minor
> complication, granted, but parsing text is always at least a slight
> annoyance), there's another problem: DVCS. i edit the field, then you close
> the ticket in
On Wed, Oct 2, 2013 at 4:16 PM, Jacek Cała wrote:
> I'd say it is as simple as it sounds: it just blocks another ticket from
> closing, meaning that when you look at the view page and see some blockers
> you may want first to check whether they've already been closed.
>
In that case, what happen
2013/10/2 Stephan Beal
> On Wed, Oct 2, 2013 at 3:51 PM, Jacek Cała wrote:
>
>> ...For those interested I report changes to the ticket table (below) and
>> view and edit pages (attached source). A remaining issue is that as
>> there're no hard db constraints on blockers there seems to be no way
On Wed, Oct 2, 2013 at 3:51 PM, Jacek Cała wrote:
> ...For those interested I report changes to the ticket table (below) and
> view and edit pages (attached source). A remaining issue is that as
> there're no hard db constraints on blockers there seems to be no way to
> verify that the blocker to
Hi all,
About 4 years ago I wrote about a missing feature -- a way to specify that
a ticket is a blocker of another ticket. There was a useful suggestion from
Brian T... time passed and recently this feature has become more and more
urgent to me, so I decided to implement it.
For those interested
On Thu, Aug 29, 2013 at 6:02 PM, Jan Jurak wrote:
> Dear developers,
>
> First thank you for nice piece of software. I am using fossil for some
> of my projects and some users wants more featured ticket system. For
> example spent time for solving the issue. What is your opinion on
> that. I am t
Dear developers,
First thank you for nice piece of software. I am using fossil for some
of my projects and some users wants more featured ticket system. For
example spent time for solving the issue. What is your opinion on
that. I am trying avoid installing another software.
TIA
--
Regards
Jan J
Hello All,
There seems to be a bug in the ticket system. Could someone verify this.
I added an "assigned_to" column into the fossil ticket system. When I
edit a ticket's "assigned_to" column and comment, an artifact is
generated (viewable in the admin/log page) but it does not seem to get
appl
Thanks Brian for some ideas. I'll see what I can do with that. As you
guessed, thinking about blockers I'd like to enforce a blocked ticket not to
be closed before all blockers and also to visualize them in ticket reports.
Cheers,
Jacek
2009/11/24 Brian Theado
> 2009/11/17 Jacek Cała :
> >
2009/11/17 Jacek Cała :
> I wonder if there is any simple way to add `blocker' feature to the fossil's
> ticketing system (I mean a list of tickets that prevent one to complete).
I'm not sure exactly what behavior a blocker feature would have, but see below.
> I tried adding 'CREATE TABLE blocker
Hi all,
I wonder if there is any simple way to add `blocker' feature to the fossil's
ticketing system (I mean a list of tickets that prevent one to complete). I
tried adding 'CREATE TABLE blocker(...)' in the Admin->Tickets->Table page
and then when creating a new ticket report it says:
* **Synta
19 matches
Mail list logo
