Hello Jan,
On Wednesday 13 October 2010, Jan Torben Heuer wrote:
> I'm sure this has already been raised here: Why is User Story
> (without Requirement) and a Requirment in the Backlog styled in the
> same way? It looks like agilo styles has styles for "parent" and
> "child" rather than requirement and user story. This makes it very
> complicated for my to find orphaned user stories and sometimes I mix
> requirements and user story.
As you noticed, by default top level items are styled differently from
child-elements. We intentionally reduced the use of colors as
identification markers and used indentation for hierarchies. If you want
to style certain backlog items (tasks, stories, requirements) in a
certain way, you can create custom CSS rules:
.tickettype-story {
background-color: ... !important;
}
or
.tickettype-requirement.ticketstatus-closed {
text-decoration: line-through;
}
Check this post on how to include your local CSS files in an Agilo
environment:
http://groups.google.com/group/agilo/browse_thread/thread/982233f94523d395/
Cheers
Robert
--
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-scrum
http://freshmeat.net/projects/agiloforscrum
You have received this message because you are subscribed to
the "Agilo for Scrum" Google Group. This group is focused on
supporting Agilo for Scrum users and is moderated by
Agilo Software GmbH <http://www.agiloforscrum.com>.
To post to this group, send email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo
