It's all about the answers!

Ask a question

Two Development Lines, Only One Can be Current


Gary Mullen-Schultz (28725536) | asked Feb 24 '09, 11:23 a.m.
I created two different development lines within a single project. They are for different applications, each on their own schedule.

Right now I can only have one current iteration for the whole project. I need to have a current iteration for each development line.

Did I configure something incorrectly, or do I misunderstand the concept of a development line?

4 answers



permanent link
Jared Burns (4.5k29) | answered Feb 24 '09, 11:59 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On Tue, 24 Feb 2009 16:28:00 +0000, garymu wrote:

I created two different development lines within a single project. They
are for different applications, each on their own schedule.

Right now I can only have one current iteration for the whole project.
I need to have a current iteration for each development line.

Did I configure something incorrectly, or do I misunderstand the concept
of a development line?


The scenario you're describing shouldn't be possible. Each development
line should be able to have a current iteration.

Please file a workitem against the Process component, including a
screenshot showing how you're being prevented from setting an iteration
as current.
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.newWorkItem


--
Jared Burns
Jazz Process Team

permanent link
Gary Mullen-Schultz (28725536) | answered Feb 24 '09, 10:35 p.m.
It started working after about 15 minutes. On its own.

We saw other, similar cases where changes didn't become "known" for a certain period of time. For example, we added a release to a project, and even some 30 minutes later it was not visible from another RTC client (RAD 7.5.1 with RTC plugin). When I tried to add it from that other box, I got an SQL insert error (as, in fact, it was already there). Refresh hadn't helped.

Same thing with an iteration we created. Another user couldn't see it (in the "Planned for" section of a new work item). After a fairly long period of time it showed up.

Any thoughts?

Thanks, Gary

permanent link
Jared Burns (4.5k29) | answered Feb 25 '09, 8:59 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On Wed, 25 Feb 2009 03:37:55 +0000, garymu wrote:

It started working after about 15 minutes. On its own.

We saw other, similar cases where changes didn't become "known" for a
certain period of time. For example, we added a release to a project,
and even some 30 minutes later it was not visible from another RTC
client (RAD 7.5.1 with RTC plugin). When I tried to add it from that
other box, I got an SQL insert error (as, in fact, it was already
there). Refresh hadn't helped.

Same thing with an iteration we created. Another user couldn't see it
(in the "Planned for" section of a new work item). After a fairly long
period of time it showed up.

Any thoughts?

Thanks, Gary


If you remember the steps you took to reproduce these problems, I would
suggest opening a bug against the "Work Item" category. They're
responsible for both Releases and the Planned For attribute.

--
Jared Burns
Jazz Process Team

permanent link
Adrian Cho (8213322) | answered Feb 28 '09, 10:44 p.m.
JAZZ DEVELOPER
I created two different development lines within a single project. They are for different applications, each on their own schedule.

Right now I can only have one current iteration for the whole project. I need to have a current iteration for each development line.

Did I configure something incorrectly, or do I misunderstand the concept of a development line?


As Jared says, this should definitely be possible. We do this ourselves in RTC. Up until recently we were iterating concurrently (and separately) with one development line for 2.0 and another for 1.0.1.1.

Your answer


Register or to post your answer.