Re: [fossil-users] limited ticketing system

On Fri, Jun 28, 2013 at 8:18 PM, reverse wrote: > I managed to configure a "read only my tickets" Fossil repository. Please > see > http://snowflakejoins.com/**fossil/private.htmlfor > implementation details > Please don't take this the wrong way

[fossil-users] limited ticketing system

Hi, In reply to the discussion on http://lists.fossil-scm.org:8080/pipermail/fossil-users/2011-November/007571.html I managed to configure a "read only my tickets" Fossil repository. Please see http://snowflakejoins.com/fossil/private.html for implementation details Please see http://snowf

Re: [fossil-users] limited ticketing

> 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, developm

Re: [fossil-users] limited ticketing

We are not using the limitations the original request suggested, though I did put in some TH1 code for the purpose of encouraging following the process flow. This was mostly to make the non-software people more comfortable. (Fossil's ticket system is quite good. The only people I personaly know wh

Re: [fossil-users] limited ticketing

On Fri, Nov 18, 2011 at 4:02 PM, Ron Wilson wrote: > In most work environments, I would not expect users outside of the > software team to be knowledgeble enough to use a JSON based "front > end" not served by either Fossil or another company server. > Yes, but "security via obfuscation" isn't a

Re: [fossil-users] limited ticketing

On Fri, Nov 18, 2011 at 5:36 AM, Remigiusz Modrzejewski wrote: > > You know that by similar funny "implications" we can "prove" that most of > Fossil is actually > redundant...  Actually, why do we even have a permission system, if Fossil is > an internal > development tool? Last I looked, the

Re: [fossil-users] limited ticketing

On Fri, Nov 18, 2011 at 5:28 AM, Stephan Beal wrote: > On Thu, Nov 17, 2011 at 10:55 PM, Ron Wilson wrote: >> >> if {$login eq $submitter} { >>      things that only the submitter is allowed to do >> } >> >> You could do similar with an assignedto field, as well. > > Yes, but... then the JSON API

Re: [fossil-users] limited ticketing

On Nov 18, 2011, at 3:41 AM, Tomek Kott wrote: > 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 th

Re: [fossil-users] limited ticketing

On Thu, Nov 17, 2011 at 10:55 PM, Ron Wilson wrote: > if {$login eq $submitter} { > things that only the submitter is allowed to do > } > > You could do similar with an assignedto field, as well. > Yes, but... then the JSON API would also have to support th1, which it doesn't (and isn't pla

Re: [fossil-users] limited ticketing

+1 for simple approach with focus to internal development --- Jiri Navratil 18. 11. 2011 v 3:44, Steve Bennett : > 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 sys

Re: [fossil-users] limited ticketing

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

Re: [fossil-users] limited ticketing

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

Re: [fossil-users] limited ticketing

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

Re: [fossil-users] limited ticketing

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

Re: [fossil-users] limited ticketing

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

Re: [fossil-users] limited ticketing

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

Re: [fossil-users] limited ticketing

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

Re: [fossil-users] limited ticketing

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

[fossil-users] limited ticketing

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