I agree. One of the strengths of the fossil ticketing system is
it's integration with the scm history, which is not what you would not
want for a customer-facing ticketing systems. I suggest using one of the
other support management systems for that and keep fossil for internal,
development use
If we have granular permissions for tickets, then we should probably also
have it for the wiki (view attachments, view history), we should also
separate attach and delete for wiki and tickets, and maybe even throw in
permissions related to the timeline and files (such as view newest view
hitsory, v
On Thu, Nov 17, 2011 at 6:56 PM, Remigiusz Modrzejewski
wrote:
>
> On Nov 17, 2011, at 6:28 PM, Stephan Beal wrote:
>> Fossil doesn't offer that level of granularity.
>
> But it should have, as this seems to be a really reasonable (and perfectly
> doable) thing to have. Thus I open a ticket (sorr
On Nov 17, 2011, at 6:28 PM, Stephan Beal wrote:
> On Thu, Nov 17, 2011 at 6:02 PM, ST wrote:
>
>> as far as I understand one can enable/disable ticket viewing completely,
>> but I don't see a way for a user to be able to see/comment/append _only_
>> to tickets submitted by him...
>>
>
> Foss
On Thu, Nov 17, 2011 at 12:28 PM, Stephan Beal wrote:
> On Thu, Nov 17, 2011 at 6:02 PM, ST wrote:
>>
>> as far as I understand one can enable/disable ticket viewing completely,
>> but I don't see a way for a user to be able to see/comment/append _only_
>> to tickets submitted by him...
>
> Fossi
On Thu, Nov 17, 2011 at 6:02 PM, ST wrote:
> as far as I understand one can enable/disable ticket viewing completely,
> but I don't see a way for a user to be able to see/comment/append _only_
> to tickets submitted by him...
>
Fossil doesn't offer that level of granularity.
--
- stephan b
On Thu, 2011-11-17 at 14:34 +0100, Remigiusz Modrzejewski wrote:
> On Nov 17, 2011, at 11:01 AM, ST wrote:
>
> > is it possible to configure fossil server so, that some clients will be
> > able only submit tickets (and even not see other tickets or maybe see
> > only tickets that they have submitt
On Nov 17, 2011, at 11:01 AM, ST wrote:
> is it possible to configure fossil server so, that some clients will be
> able only submit tickets (and even not see other tickets or maybe see
> only tickets that they have submitted)? This mode would be useful for
> customers whom you want to submit bug
And, most of all, for users it makes documentation just a click away.
Cheers,
Jacek
2011/11/16 Steve Havelka :
> On 11/16/11 4:11 PM, Ron Wilson wrote:
>>
>> On Wed, Nov 16, 2011 at 4:15 PM, Jacek Cała wrote:
>>>
>>> and wonder why
>>> fossil is by default so humble to not include a link to
On Nov 17, 2011, at 2:04 AM, Gareth Roberts wrote:
> Hi Will,
>
> fossil open --nested allows opening a fossil within an existing checkout.
> This question came up earlier this week as well; it may be worth looking at
> the archives.
> Solutions included fossil open --nested and scripting a che
Hi Will,
fossil open --nested allows opening a fossil within an existing checkout.
This question came up earlier this week as well; it may be worth looking
at the archives.
Solutions included fossil open --nested and scripting a checkout of
external dependencies.
Cheers,
Gareth
On Thu, 17
Hi,
is it possible to configure fossil server so, that some clients will be
able only submit tickets (and even not see other tickets or maybe see
only tickets that they have submitted)? This mode would be useful for
customers whom you want to submit bug reports without being able to
observe the wh
12 matches
Mail list logo
