Daragh Fitzpatrick | 1 Jun 2004 17:14
Favicon

RE: Assign-to: field

I've worked out how to do it. Can I put a branch in the repository?

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick        Daragh-3aI4IeFKCVr2fBVCVOL8/A@public.gmane.org         (773) 702-8976

Solutions Architect                      NSIT Administrative Systems
Renewal Projects and Architecture              University of Chicago
--------------------------------------------------------------------

 

From: trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org [mailto:trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org] On Behalf Of Daragh Fitzpatrick
Sent: Friday, May 28, 2004 3:39 PM
To: trac-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org; Daragh-t4+EzPmVLfD2fBVCVOL8/A@public.gmane.org
Subject: [Trac] Assign-to: field

Has anyone implemented the assign-to field as a dropdown? I'm trying to do it, but clearsilver is making it non-obvious...

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick        Daragh-3aI4IeFKCVr2fBVCVOL8/A@public.gmane.org         (773) 702-8976

Solutions Architect                      NSIT Administrative Systems
Renewal Projects and Architecture              University of Chicago
--------------------------------------------------------------------

 

From: trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org [mailto:trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org] On Behalf Of Daragh Fitzpatrick
Sent: Friday, May 28, 2004 3:05 PM
To: trac-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org
Subject: RE: [Trac] Tickets Usage Question

I looked into this recently, and the ticket state workflow is coded into the Ticket.py module. I.e., you would be changing the workflow of the entire ticket module.
 
I would like to suggest that resolutions be something that is configurable, though.
 
I have also gotten a request that the 'assign to:' field be a dropdown of valid assignees.

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick        Daragh-3aI4IeFKCVr2fBVCVOL8/A@public.gmane.org         (773) 702-8976

Solutions Architect                      NSIT Administrative Systems
Renewal Projects and Architecture              University of Chicago
--------------------------------------------------------------------

 

From: trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org [mailto:trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org] On Behalf Of Lee, Kevin
Sent: Friday, May 28, 2004 12:38 PM
To: trac-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org
Subject: RE: [Trac] Tickets Usage Question

No one responded to my email, so I think that means everyone does not have any problems with the current implementation of the Trac tickets.  I can see where the simplified model may be easier to use with small projects, but as projects grow, this seems like it could be insufficient.  Subversion uses this state model for their issue tracking: http://subversion.tigris.org/scdocs/issue_lifecycle.html

 

So my next question would be: How hard would it be to add more states to the ticket status? 

 

Thanks!  Kevin

 

-----Original Message-----
From: trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org [mailto:trac-bounces-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org] On Behalf Of Lee, Kevin
Sent: Friday, May 14, 2004 11:49 AM
To: trac-/d+y5hMAhVIyk1uROcNW80EOCMrvLtNR@public.gmane.org
Subject: [Trac] Tickets Usage Question

 

Hi,

 

I’m trying to figure out how we can use Trac Tickets for our projects.  I’m not sure how to model the state that a bug has been fixed and is ready for verification by QA.   A bug is typically not considered resolved until it has been included in a build and verified by QA. 

 

Also, I’m used to having a way to know when a fix for a bug is ready to be built (ie. It has been committed).  This is not as important as the ready for QA state.

 

I’m used to the following use case:

                                                                                                TRAC

1)       QA gets a build (labeled BUILD_A) and starts testing

2)       QA finds a bug and files a bug against build BUILD_A       New Ticket

3)       Developer investigates bug                                             

a.       Not a problem – user error                                  Resolved - invalid

b.       Works for me                                                     Resolved - WorksForMe

c.       Finds issue                                                       Accepted

4)       Developer releases fix for bug                                          ???? – ready to build – assign to the build mgr

5)       Bug fix goes into a new build – BUILD_B                          ???? – ready to verify – assign to the tester

6)       QA gets build BUILD_B and retests bug against fix                                  

7)       Bug is either

a.       Fixed                                                                Resolved – fixed

b.       Needs more fixing                                              Reopened ?

 

Is there a way in the current Trac setup to allow this use case?  How are other people using Trac?

 

Also, I see a button for accepting a ticket, but whenever I reassign a ticket to someone, it automatically gets set to accepted.  Is there a config somewhere that I need to set to allow the assigned person to accept a ticket?

 

I’m just a beginner with Trac.  Is it easy to modify the configuration of the web pages and/or the database to add this kind of functionality?

 

Thanks!  Kevin Lee

kdlee-zC7DfRvBq/JWk0Htik3J/w@public.gmane.org

 

_______________________________________________
Trac mailing list
Trac@...
http://lists.edgewall.com/mailman/listinfo/trac
Emmanuel Blot | 2 Jun 2004 13:02
Picon
Favicon

ACL & group

Hi,

Is there any plan to implement group management in Trac ACL ?

The granularity of a single user is nice, but somewhat difficult to manage 
from an administrator perpective. It would be nice if Trac were able to handle 
group in addition to single user permissions.

As we use LDAP authentication on our web server, I've added group management 
to Trac ACLs. Group permissions are defined in the SQLite permission table, as 
it is for single user. I've used the usual character to denote groups among 
users:  <at> . 
A 'group' is therefore prefixed with a ' <at> ' sign, like ' <at> administrators'

In order not to change the current Trac implementation, I did not change the 
way user permissions are stored and retrieved. However, this may not scale 
well to large directories with many different groups.

trac-admin does support 'usernames' with  <at>  sign.

The current implementation does the following (in perm.py)

if user 'anonymous': perform the same code than original trac code
if user not 'anonymous':
   open a connection to the LDAP directory
   retrieve the list of all available groups in the LDAP directory (*)
   filter out all groups the user not belongs to (from LDAP group lists)
   for each group (and) user
      read and use permissions of the group as defined in SQLite permission 
table

This way, if user belongs to group  <at> agroup (in LDAP), user is assigned 
permission from group  <at> agroup (in SQLite).

(*): this may not fit well to directories using many different group in the 
same base DN. 

As ACL are tested for each cgi request, this may lead to poor performances. 
I do not know how to improve this. Please let me know if there is a better way 
to use group permissions.

Emmanuel.

--

-- 
Felix Collins | 3 Jun 2004 01:57

Creating multiple Trac projects

Hi,
First of all congratulations on a great project! I had a Trac database 
up and running in a couple of days.  Admittedly I had already 
implemented a Subversion system, but other than that I am a web server 
newbie.

Now I am trying to set up a multi project system for the company.  What 
I envision is allowing suitably authorised users to create projects via 
a web page.  When a project is created a subversion repository will be 
set up and a trac database created and configured. The 
TracMultipleProjects page of the wiki goes part of the way and I have 
got that Apache config up and running.  The bit I am struggling with now 
is automatically setting up the Trac database.  There is no 
non-interactive way of doing an initenv.  Once the environment is 
initialised I can get the project ini file and edit that, but changing 
user access privileges and other trac-admin config is a bit harder 
(requiring direct access to the database I think. arrgh!).

Has anyone written any code that will set up priviledges based on 
command line arguments or a file?

Another idea which should be quite easy to implement is to add more 
power to the priviledges "add" and "remove" commands by allowing regexp 
matching.  Does SQLite support some sort of wild cards? If so you could 
just pass that straight through.

It would be useful to be able to change all of the configuration using 
command line arguments to trac-admin as this would enable easy scripting 
  for administration purposes.

If no one has done any of this I might just have to learn python and 
dust of my severley limited SQL knowledge. ;-) Is the database schema 
documented anywhere?

Thanks for your time...

Felix
Daragh Fitzpatrick | 3 Jun 2004 04:59
Favicon

RE: Creating multiple Trac projects


I would like to do groups, but don't know how to do it (admittedly my
project is small, so I was lazy about looking at the documentation on how to
do it, if possible) 

The way I set up permissions is to create a file, and copy and paste the
list of commands into the trac-admin session - so yes, it requires
interaction.

The approach I'd suggest is looking at the python code for trac-admin, and
coding something based around it.

That said, it seems to be possible to make trac-admin command-line calls in
UNIX - our current config is Windoze.

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick        Daragh@...         (773) 702-8976

Solutions Architect                      NSIT Administrative Systems
Renewal Projects and Architecture              University of Chicago
--------------------------------------------------------------------
-----Original Message-----
From: trac-bounces@...
[mailto:trac-bounces@...] On Behalf Of Felix Collins
Sent: Wednesday, June 02, 2004 6:57 PM
To: trac@...
Subject: [Trac] Creating multiple Trac projects

Hi,
First of all congratulations on a great project! I had a Trac database up
and running in a couple of days.  Admittedly I had already implemented a
Subversion system, but other than that I am a web server newbie.

Now I am trying to set up a multi project system for the company.  What I
envision is allowing suitably authorised users to create projects via a web
page.  When a project is created a subversion repository will be set up and
a trac database created and configured. The TracMultipleProjects page of the
wiki goes part of the way and I have got that Apache config up and running.
The bit I am struggling with now is automatically setting up the Trac
database.  There is no non-interactive way of doing an initenv.  Once the
environment is initialised I can get the project ini file and edit that, but
changing user access privileges and other trac-admin config is a bit harder
(requiring direct access to the database I think. arrgh!).

Has anyone written any code that will set up priviledges based on command
line arguments or a file?

Another idea which should be quite easy to implement is to add more power to
the priviledges "add" and "remove" commands by allowing regexp matching.
Does SQLite support some sort of wild cards? If so you could just pass that
straight through.

It would be useful to be able to change all of the configuration using
command line arguments to trac-admin as this would enable easy scripting
  for administration purposes.

If no one has done any of this I might just have to learn python and dust of
my severley limited SQL knowledge. ;-) Is the database schema documented
anywhere?

Thanks for your time...

Felix
_______________________________________________
Trac mailing list
Trac@...
http://lists.edgewall.com/mailman/listinfo/trac
Felix Collins | 3 Jun 2004 05:11

Re: Creating multiple Trac projects

Daragh Fitzpatrick wrote:

> The way I set up permissions is to create a file, and copy and paste the
> list of commands into the trac-admin session - so yes, it requires
> interaction.

What about doing an "initenv"?

> The approach I'd suggest is looking at the python code for trac-admin, and
> coding something based around it.

Already had a look at the source.  It doesn't look to hard so maybe I'll 
have a hack at it.

> That said, it seems to be possible to make trac-admin command-line calls in
> UNIX - our current config is Windoze.

Woops, yep you can make command line calls. I guess all I need is for 
initenv to take a command line arg.  Maybe a file like in .ini format 
that specifies all the stuff that it asks for.

Felix
Felix Collins | 3 Jun 2004 05:29

Trac Repository Browser bypasses SVN permissions

Hi,

If you have Subversion set up using an Apache server with the 
authz_svn_module providing directory level access control and you set up 
Trac, the Trac browser neatly bypasses the access control.

This is quite a likely scenario as you will no doubt be running Trac on 
the same Apache server as you Subversion install.

It is only a problem if you don't want all your users to be able to read 
the whole repository, but in this case it renders the Trac repository 
browser unusable.  My example is a private company project with nothing 
is visible to unauthenticated users some with r/w and some only read 
privileges.  We also have a contractor who should only be allowed to 
read and write under certain directories on one project.

Is there anyway that Trac could check with the authz_svn_module to see 
if it is OK to browse a particular part of the repository?  Is there a 
library in Subversion for this?

Which level of access does Trac use to read from the subversion 
repository: repository layer, repository access layer or client layer?

Cheers,
Felix
Christopher Lenz | 3 Jun 2004 09:03
Picon
Picon
Gravatar

Re: Trac Repository Browser bypasses SVN permissions

Hi Felix,

Am 03.06.2004 um 05:29 schrieb Felix Collins:
> Hi,
>
> If you have Subversion set up using an Apache server with the 
> authz_svn_module providing directory level access control and you set 
> up Trac, the Trac browser neatly bypasses the access control.
>
> This is quite a likely scenario as you will no doubt be running Trac 
> on the same Apache server as you Subversion install.
>
> It is only a problem if you don't want all your users to be able to 
> read the whole repository, but in this case it renders the Trac 
> repository browser unusable.  My example is a private company project 
> with nothing is visible to unauthenticated users some with r/w and 
> some only read privileges.  We also have a contractor who should only 
> be allowed to read and write under certain directories on one project.
>
> Is there anyway that Trac could check with the authz_svn_module to see 
> if it is OK to browse a particular part of the repository?  Is there a 
> library in Subversion for this?

see http://projects.edgewall.com/trac/wiki/FineGrainedPermissions

> Which level of access does Trac use to read from the subversion 
> repository: repository layer, repository access layer or client layer?

The repository layer (RA isn't available because the Python bindings 
are not usable yet, IIUC).

Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
Luc Pelletier | 3 Jun 2004 21:44

Diff on Windows & Viewing .BAS files in browser

Hello,

I have recently installed Trac to evaluate it and I must say that I'm very impressed with it so far!

That being said, I've encountered a few issues (I'm running on Windows 2k):

1. Diffs between files are not displayed. I have tried downloading and installing the latest diffutils from gnuwin32.sourceforge.net but that didn't solve my problem. I can run 'svn diff' from the command-line and it works fine. I can also run 'diff' from the command-line (diff is in the PATH).

2. When I browse the source code in SVN using the Trac browser, it doesn't display the contents of the file when I click on a file that has a .BAS extension. Other extensions (.CLS, .FRM) work fine.

I'm running the latest version of Subversion (1.0.4).

Any ideas?

Thanks.



---
Luc Pelletier
Software Engineer
Dipix Technologies


============================================================================
This email was scanned and certified as free from any known malicious data but understand that
any files attached and opened by you are at your own risk!
The information contained in this message is intended only for the personal and confidential use
of the designated recipients named herein. As of May 25, 04 if this disclaimer is not included than this
email did not originate from Dipix Technologies Inc.

_______________________________________________
Trac mailing list
Trac@...
http://lists.edgewall.com/mailman/listinfo/trac
Felix Collins | 3 Jun 2004 22:44

Re: Trac Repository Browser bypasses SVN permissions

Thanks for that Christopher.  It is great to see someone was on to the 
problem before I really realised it!  I guess I should have searched for 
active issues on this before posting. ;-)

Eagerly awaiting an announcement on completion....

Cheers,
Felix

Christopher Lenz wrote:

> 
> see http://projects.edgewall.com/trac/wiki/FineGrainedPermissions
> 
Jonas Borgström | 3 Jun 2004 23:11
Favicon

Trac 0.7.1 Released

Trac 0.7.1 'Argento' Release Notes
===================================
Jun 3, 2004

Edgewall Software is pleased to announce, Trac 0.7.1 'Argento'.

Trac is a minimalistic web-based software project management and 
bug/issue tracking system. It provides an interface to the Subversion
revision control systems, an integrated wiki, flexible issue tracking
and convenient report facilities.

Trac allows wiki markup in issue descriptions and commit messages,
creating links and useful structure between bugs, tasks, changesets,
files and wiki pages.  A timeline view presents all project events in
chronological order, making tracking progress or getting an overview of
a project easy.

For more information, please visit the main Trac web site:

   <http://trac.edgewall.com/>

The software, published under the GNU General Public License, is
available at:

   <http://projects.edgewall.com/trac/download/>

Please report problems and provide feedback in the project issue
tracker:

   <http://projects.edgewall.com/trac/>

For questions, comments and user discussions, please use the Trac
mailing list. List information, subscription and archive available at:

   <http://projects.edgewall.com/trac/wiki/MailingList>

What's New
----------
0.7.1 'Argento' is primarily a bug-fix release for 0.7. Also included in
this release is experimental support for running Trac in mod_python.
This allows higher performance and shorter response-times, especially
when serving many concurrent users.

A summary of major changes for this release:

  * Bugfixes for 0.7
  * Fixes security hole in auth.py
  * Experimental support for mod_python
  * Added support for more MIME-types

For a more complete list of improvements, see the ChangeLog at:

  <http://projects.edgewall.com/trac/wiki/ChangeLog>

About Edgewall
--------------
Edgewall Software is an independent software development company
specialized in Linux and open source technologies. Edgewall provides
software development capabilities and consultancy to clients worldwide,
on both short term basis and in long term strategic partnerships.

Specific areas of expertise include:

     * Python development, including Python extensions and integration.
     * Web services and application development.
     * C and C++ application development for UNIX and Linux.
     * Cross-platform application development and porting.
     * Open Source development practices, methods and tools.

Edgewall also offers professional Trac support and consulting, including
customization, integration and custom feature development.

For more information, visit our web site at <http://www.edgewall.com/>
or email us at <mailto:info@...>.

Acknowledgements
----------------
Many thanks to the growing number of people who have, and continue to,
support the project. Also our thanks to all people providing feedback
and bug reports that helps us make Trac better, easier to use and more
effective.

Without your invaluable help, Trac would not evolve. Thank you.

Finally, we hope Trac will prove itself useful to like-minded
programmers around the world, and that this release will prove an
improvement over the last.

Please let us know. :-)

/The Trac Team <http://trac.edgewall.com/>
--

-- 
Jonas Borgström    | Edgewall Software
jonas@... | Professional GNU/Linux & Open Source Consulting.
                    | http://www.edgewall.com/

Gmane