Trying to build hierarchy

[Secam]

Hello,

I am new to Agilo so I started playing with the tool.
First goal: create a custom hierarchy.
Here is how I plan to run the project (a bit of know how). The
requirement is at the top but requirements are very high level and
some times mean a lot. The user story for me is a collection of tasks
that need to be accomplished to say something is done to the product
owner. Let me give you an example:
User Story "Allow administrator to do XYZ using ABC". Ok so this
means:
Task1: Design feature
Task2: Develop feature
Task3: Develop unit test
Task4: Run unit test
Task5: Create a description of the feature
Taskt6: Create automated test
Task7: ...
As one can see the tasks are for all members of the team, DEV, DOC, QE
etc.
So for each even small thing like bug or enhancement there is a set of
cross functional tasks that need to be completed. In such case the
user story can be "Address this bug or RFE".
In my view user story is a pretty low level item. There should be a
way to inject some grouping mechanism between high level requirement
and a user story.
Is it possible?
I created a new ticket type: phase
I created new Agilo type: Phase. It has nothing specific since it is
just an aggregation mechanism
Now when I create a requirement I want to be able to automatically
create "Phases" and link them to "Requirements".
The system uses Requirement->User Story->Task.
I want Requirement->Phase->User Story->Task.
I added links - it did not help.
I removed the link that associates Requirement to user story but
system still knows about it somehow.
It seems like something is broken there.
Any help will be appreciated.

[Secam]

Hi,

I continued my experiments.
I removed all pre-configured types and started with my own.
Created ticket types I need.
Created agilo types (specified that each type can have reference and
can be referenced)
Added managed links I need as described below.
The items just do not link together.
I can put the values in to link fields of the two objects to point
from one to another but system does not recognize a valid link. It
just ignores it.

Very confusing I should say...

Thanks
Secam

[Martin Häcker]

On 06.11.09 21:40, Secam wrote:
> Hi,
>
> I continued my experiments.
> I removed all pre-configured types and started with my own.
> Created ticket types I need.
> Created agilo types (specified that each type can have reference and
> can be referenced)
> Added managed links I need as described below.
> The items just do not link together.
> I can put the values in to link fields of the two objects to point
> from one to another but system does not recognize a valid link. It
> just ignores it.
>
> Very confusing I should say...

I noticed that I had to restart trac after applying these configuration
changes to make them work correctly.

Does that help you too?

Regards,
Martin

[Dmitri Pal]

Hi,

I do not have access to the machine to be able to perform administrative tasks on the instance.
If the tool requires its own restart there should be a button within the admin interface to do it.
I do not even know where it is deployed and what machine it is running on.
Requiring power user to also be an admin on the web server is wrong.
These are completely different roles in the enterprise.

Thanks
Dmitri

--
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
-----
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to ag...@googlegroups.com
To unsubscribe from this group, send email to
agilo+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en

[Andrea Tomasini]

On 9 Nov, 2009, at 17:49 , Dmitri Pal wrote:

> Hi,

Hi,

> I do not have access to the machine to be able to perform
> administrative tasks on the instance.
> If the tool requires its own restart there should be a button within
> the admin interface to do it.
> I do not even know where it is deployed and what machine it is
> running on.

Actually if you change the configuration, and that is successfully
completed, you will trigger a restart, so there is no need to have a
button.

> Requiring power user to also be an admin on the web server is wrong.

Agree :-)

> These are completely different roles in the enterprise.

Not always ;-)

> Thanks
YAW

> Dmitri
ANdreaT

[Dmitri Pal]

This is true but the tool should assume that they are different.

 

> Thanks
YAW

> Dmitri
ANdreaT

[Andrea Tomasini]

On 9 Nov, 2009, at 19:58 , Dmitri Pal wrote:

Hi Dmitri,

> This is true but the tool should assume that they are different.

The tool is not assuming anything to stay on the safe side... it just
does what is needed, as good as it can, and is looking forward for any
improvement the community will be willing to submit, or suggest or
whatever else, valuable :-)

So di you solve your problems with links? Have you tried first to make
the hierarchy you want to make in a freshly downloaded VM for example,
to try to isolate specific system problem, from something that is
really a tool issue? To create links as to create items you need to
have the CREATE_[YOUR_TICKET_TYPE] rights, or the link won't be
created, if I remember correctly. We are thinking about splitting
this, but for now it is still all in "I can write" and "I can only
read" or "I can do nothing" with this type...

HTH
ANdreaT

[Dmitri Pal]

On Mon, Nov 9, 2009 at 2:07 PM, Andrea Tomasini <andrea....@agile42.com> wrote:

On 9 Nov, 2009, at 19:58 , Dmitri Pal wrote:

Hi Dmitri,

> This is true but the tool should assume that they are different.

The tool is not assuming anything to stay on the safe side...

 

 

To be on the safe side the tool should not assume that person who is configuring it has access to the machine the instance is running in.

Assumption that someone can restart the instance manully is wrong.

This is it.

 

it just
does what is needed, as good as it can, and is looking forward for any
improvement the community will be willing to submit, or suggest or
whatever else, valuable :-)

 

 

I know how it works :-)

 

 

 

 

So di you solve your problems with links?

 

 

No.

 

 

Have you tried first to make
the hierarchy you want to make in a freshly downloaded VM for example,
to try to isolate specific system problem, from something that is
really a tool issue? To create links as to create items you need to
have the CREATE_[YOUR_TICKET_TYPE] rights, or the link won't be
created, if I remember correctly. We are thinking about splitting
this, but for now it is still all in "I can write" and "I can only
read" or "I can do nothing" with this type...

 

I had highest privilege. I was an admin.

I had a whole instance set to myself. 

I spent about a day playing with the tool trying to click by way through.

This is about as much as I can afford.

 

At this point I am willing to try again if anyone would be so kind to point me to some step-by-step process on how to add more hierachies.

I can promise I will:

 

a) Try it

b) Add to it if something is missing or if I see if some comments would be benificial

c) File bugs if there are bugs

d) Test bug fixes later

 

 This is about as much as I can dedicate to it.

 

Thank you

Dmitri

 

HTH

[Martin Häcker]

Hi Dmitri,

> To be on the safe side the tool should not assume that person who is
> configuring it has access to the machine the instance is running in.
> Assumption that someone can restart the instance manully is wrong.
> This is it.

I am sorry if I have upset you - I just wanted to suggest a workaround.

A different workaround I just tested successfully is to go to the Agilo
General preference pane and click save there (no change in settings
required).

This forces the configuration to be reloaded and should work around this
bug.

> No.

Please report if that solves your problem. The steps you took to
configure this where quite correct, so I really guess that this should
fix the behavior you are seeing.

In the meantime I have entered this bug report to track fixing of this
issue: <https://dev.agile42.com/ticket/930>

Best Regards,
Martin