Community
Participate
Working Groups
Trac should recognize stories as a task type. Also if subtasks of stories are created the type should default to task.
Created attachment 173501 [details] fix
Created attachment 173502 [details] mylyn/context/zip
Changes committed to e_3_4_m_3_4_x branch and head.
Created attachment 173608 [details] additional change for error type
Steffen, what is the rationale behind this ticket. We also use the concept of "Stories" from the Extreme Programming paradigma. But we did implement them in Trac using keywords. Thanks, Jörg
I realize that there are many possible ways stories are represented in Trac as the repository itself does not specify a standardized way of doing that. I opted to support this through the type since it seemed obvious and know of several installations where that is the case. That said, I'd be happy to support keywords as well if the schema is reasonably generic.
(In reply to comment #6) > I realize that there are many possible ways stories are represented in Trac as > the repository itself does not specify a standardized way of doing that. I opted > to support this through the type since it seemed obvious and know of several > installations where that is the case. That said, I'd be happy to support > keywords as well if the schema is reasonably generic. Thanks for replying prompty. I wonder whether the type "story" has some special semantics inside the Trac connector or whether it just works as "defect" or "enhancement".
> Thanks for replying prompty. I wonder whether the type "story" has some special > semantics inside the Trac connector or whether it just works as "defect" or > "enhancement". No special semantics, just a different decoration in the task list and the type for sub-tasks of stories is set to task (not story).
