Agilefant.org

Features requested

Daily Work for several persons or a team

8.5.2008 Vilant Systems

"The ability to see the load of the whole team from one report would be very useful for resourcing, especially when developers work on several overlapping projects."

This is in the backlog. Will be implemented sometime after hierarchical backlog items, unless further requests arrive

Ability to export issue lists from backlogs to csv files

8.5.2008 Vilant Systems

Agreed, exporting the data from 'Fant would be useful for several purposes. Will most likely be implemented sometime during Agilefant 2009 Testarossa.

Adding responsibles for todo's

Requested by Seppo Sahi / G-Cluster 14.4.2008

So far, we think that this is not necessary. Just make smaller backlog items.

However, a couple of points for discussion on how this should work, if it were to be implemented:

1) Should you be able to mark as responsible for a todo
  a) any user? if so, should he be assigned to the backlog item as well?
  b) only those users that have been assigned to the project?
  c) only those users that have been assigned to the backlog item?
  d) other?

2) Should these somehow be reflected in the Load calculations?

Currently, the effort remaining for a task is split evenly among those responsible for it. We think that this would be the way to do it also in the future, but are asking your opinion for the sake of argument.

User rights mgmt

Requested by Humair Quadri / Exceed Digital Systems 17.9.2008

The question about restricting user access to some parts of system is raised every now and then. So far we have found other things more valuable to implement, and are somewhat skeptical weather restricting user access is aligned with agile principles. We have taken the approach that every employee is trusted and if this trust is broken it is an organizational problem thet shouldn't be tackled with a tool in the first place.

However, there are some business situations where restricting users access to some parts of the systems may be justified. The following are our current thoughts on how adding user rights mgmt to Agilefant should be approached.

User rights affect almost everything in the system, so the simplest approach that does the trick should be taken. Even the simplest specification tends to expand rapidly. Below are our present thoughts in a step-by-step manner. Here goes...

1. There should be two levels of access rights: unrestricted ( the user is allowed to do anything - this is the current situation in 1.5 for all users) and restricted (the user can see only those projects she is assigned to - see step 3 below).
2. Projects can be set as public (default) or classified
3. Restricted users see all public projects and those classified projects they have been assigned to; Things to be considered:

• Restricted users shouldn't see the Dev Portfolio page or private projects should be hidden from there
• Restricted users still might have Backlog Items assigned to them in private projects they haven't been assigned to. Thus such items and projects/iterations should be hidden from the Daily Work page
• Restricted users access to Timesheets should also be thought. So that they cannot generate reports for private projects they are not assigned to
• The Roadmap in Product page should be modified so that information of private projects isn't shown to restricted users
• Restricted users must not be able to create new users

We have not yet examined what this means source-code-wise is. But if the above specification would solve your problem, you should start by examining the Spring Security Framework which is the authentication mechanism used in the Agilefant. When you hit some specific issues please feel free to ask us.