There is some confusion in Stories in Agilefant.
When Story is inside the Project, I can assign it only TODOs, but no Tasks.
When Story is inside the Iteration, I can assign it a Task and inside the Task there will be TODOs.
The question is: why I cannot assign a Task to Story inside the Project?
And why TODOs have no Estimation time?
Questions are connected: if I divide my Story to some parts, I wish to assign them an Estimate.
So either Estimation to TODOs, or Tasks in the Project Story 
or both
This page
Other pages
Account
New
Administration
Comments (12)
Dec 02, 2009
Jarno Vähäniitty says:
These phenomena are due to some legacy reasons; the conceptual model in the 1.x ...These phenomena are due to some legacy reasons; the conceptual model in the 1.x -series was not fully similar to scrum.
You might want to try out the latest alpha of Agilefant 2.0, at least if you yet have not used Agilefant 1.6.2 very much; the conceptual model is much better there.
1.6.2 won't be changed any more, all our work is going into 2.0.
Other comments, anyone?
Feb 23
Patrick Moench says:
As of right now (Feb 23, 2010) Your bug tracker still shows this as a "new" issu...As of right now (Feb 23, 2010) Your bug tracker still shows this as a "new" issue http://www.agilefant.org/mantis/bug_view_page.php?bug_id=58
"0000058: User should be able to add tasks to a story even if story not in a sprint"
Do you know if there are plans to work on this? So far Agilefant is the best agile tool that I've looked at, but my project lead wont use it without this feature. Thank you.
Feb 24
Jarno Vähäniitty says:
This issue has - to some degree - been addressed in 2.0. Which version of Agilef...This issue has - to some degree - been addressed in 2.0. Which version of Agilefant are you currently using?
Would you also explain the practical situation in which you want to add tasks to non-sprint stories? This helps understand the actual need & suggest the solution.
Feb 24
Ilkka Lehto says:
Actually this issue has not been addressed in 2.0, sorry. I discussed the issue ...Actually this issue has not been addressed in 2.0, sorry. I discussed the issue shortly with Pasi and we concluded that the tasks in the project level would be rather tricky. Tasks could be enabled for leaf stories pretty easily, but the problem is that there is no way of accessing tasks in the story tree. So, once a child story is created a bunch of tasks would become unaccessible if the tasks are enabled in the project level.
But as said, it would help us significantly if you would describe how you use stories and tasks. We have learned that there is a fascinating amount of work-a-rounds out there and in order to help you we first need to understand your situation.
Feb 24
Patrick Moench says:
Thanks for the quick responses. I noticed the issue with your demo server, then ...Thanks for the quick responses. I noticed the issue with your demo server, then I installed my own 2.0 alpha 5 server hoping that it would be fixed there. But like Ilkka said, nothing has been done there.
Keep in mind that I'm fairly new to agile and scrum, so I might have some misconceptions on how this is supposed to work.
We want to be able to setup a project backlog with all of the stories and their associated tasks. Then we would move these stories to sprints when we can (when we know developers and other resources will be available). Some stories might never make it into sprints, but we want to capture any estimates and task breakdowns just in case. Other stories might be placed in a future sprint, only to be removed due to time/resource constraints and/or higher demand for other features. I would think that these stories would be placed back into the project backlog for future consideration. Again, we don't want to lose (or in this case, hide) the estimates and task breakdowns.
If tasks could be enabled for leaf stories, I think that would be good enough for us. Maybe make it an option in the settings?
Feb 25
Ilkka Lehto says:
Thanks for the description. Your situation is pretty much the opposite of the "n...Thanks for the description. Your situation is pretty much the opposite of the "normal" agile approach. One big point of agile software development is to provide better reaction to change by reactive and continuous planning. Instead of big upfront planning, only rough plans are done in the long term and detailed planning is done only in the last responsible moment (i.e. where the decisions cannot be prolonged and we have the most information and knowledge available). Plans are refined only as projects start and further refined in iteration planning. The finest level of detail is added during the iterations. Tasks are meant to provide the finest level of detail. The assumption is that the agile team does the task-level planning, again a "normal" agile practice. The self-organizing and cross-functional development team is responsible for the implementation details, not a project manager or any other manager. If detailing is needed in the project level, it is supposed to be done by splitting the stories i.e. creating child stories (thus creating the story tree).
Your feature request is feasible and we'll take it under consideration. However, this feature is rather low priority compared to the work that must be completed in order to release the 2.0. So, we are not making any commitment considering this feature in the next release.
Feb 25
Anonymous says:
I think it is very common to have tasks also at project/product level. For examp...I think it is very common to have tasks also at project/product level. For example in iteration planning we see that all initially included stories do not fit in the sprint, so we need to move some stories back to the backlog. In this case we don't want to lose the already made tasks. An another use case is when all stories weren't completed in the sprint and we need to move them to the backlog.
Also in some support issues we create the tasks before scheduling them to the sprint.
Perhaps it is just our bad process, but to us this is the most annoying limitation currently in Agilefant.
Feb 25
Jarno Vähäniitty says:
I guess I meant that the issue has not been addressed in 2.0, but there it is a ...I guess I meant that the issue has not been addressed in 2.0, but there it is a bit easier to live with
You can currently have tasks for stories that are on the project or product levels...you just can't access or see them. When you move the story to an iteration, you can again edit the tasks.
Feb 25
Patrick Moench says:
Thank you for considering my case. We're still transitioning to agile (or agile-...Thank you for considering my case. We're still transitioning to agile (or agile-like) development, so maybe we can take it farther and not plan so many details up front for future projects/releases. Hopefully we can make it work with the requirements that are placed upon us by the other companies we work with/for. If not, then it would seem that agile is not for us.
For the time being, we were thinking of creating a "dummy" inactive sprint that we could place all of our stories with tasks into. Then we could move stories from that sprint to the real sprints as needed. Do you see any repercussions of taking this approach as a workaround for now?
Feb 26
Ilkka Lehto says:
Could elaborate even further what your tasks are alike? Are they tasks like "Uni...Could elaborate even further what your tasks are alike? Are they tasks like "Unit test for businessTransferObject, 30min"? Or are they more like "Design UI for feature X, 12h"? If your tasks are rather large, you might consider splitting your project level user stories into more detailed one. But if your tasks are something like 10min - 120min then I would suggest the workaround you described.
Feb 26
Patrick Moench says:
Some tasks are large, others are small. I agree, the larger ones could become su...Some tasks are large, others are small. I agree, the larger ones could become sub-stories. I'm planning to move everything into agilefant today so I'll give that a try.
One more question, will my projects survive an upgrade from alpha 5 to the beta and then the release when they become available?
Thanks.
Feb 28
Ilkka Lehto says:
Upgrading is possible. Some database scripts might be needed, but they are provi...Upgrading is possible. Some database scripts might be needed, but they are provided with the release packages.
Add Comment