What would be a good approach to limit valid associated Planned For releases?
In our source code deliver to stream operations behavior, we currently require developers to associate work items to an iteration, i.e.:
This works good but we want to increase the restriction to only allow assocation to an active iteration. Unfortunately, we have multiple active iterations and as far as I can tell there can only be one "current iteration"
I suspect there is some sort of custom validation I could write? Could someone point me in the right direction? I don't want to get into creating multiple teams and team timelines and some sort of three levels of redirection in order to define multiple current iterations. I think I just want to learn more about custom validation and not sure where to look first.
|
Accepted answer
Ralph Schoon (63.4k●3●36●46)
| answered Dec 09 '14, 2:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Andy,
Sam's suggestion is actually to create an advisor. The Extensions workshop is just explaining a follow up action, but advisors are pretty much the same. Here is an example based on the Extension Workshop: http://rsjazz.wordpress.com/2014/05/26/only-owner-can-close-workitem-advisor/ Now, there are server side advisors, but there are also client side advisors. They would need to be installed into any Eclipse client. They are needed, if the data required is only available on the client (like if there are unused imports). I would usually prefer a server side advisor if possible. But in your case a client side advisor could be the solution. I'd check with the team running the servers, if there is any chance to deploy on the server, however. Andy Jewell selected this answer as the correct answer
Comments Thank you for the link, that article is packed with information, I'll need to digest slowly but I'm encouraged by the step-by-step instructions. Thanks! |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
can u explain more 'active' iterations? cause I think you can have only one per timeline, its the one that is occurring right now (time based)
I think the javascript extensions do not support manipulation iterations.. but the java server side extensions do..
see https://jazz.net/library/article/1000
i think you're right about only one current iteration per timeline. My reference to "active" iterations was to my requirements, not to any capability that I was aware of. In terms of explanation, we have multiple active iterations (which we actually use more like a release) going on at any point in time. This is why I wanted to find a way to deal with multiple "current" iterations.
I guess to look at it, I have another restriction since I don't really have access to the server. Our server is managed by an enterprise team and making changes to it would either be impossible or extremely slow (administratively). In scratching around I ran into the possibility of using an Advisor. Will read more into that though I'm worried that would also be a server-based solution.