It's all about the answers!

Ask a question

Release (Found In) field


Susan Hanson (1.6k2201194) | asked Jan 12 '11, 12:29 p.m.
In a work item there is a "Release" object which is normally shown in the "Found In" presentation in the layouts. For our project, we have none defined, so all we get is "Unassigned".

I'd like to define "Releases" in my project to coincide with our deliverables and then use the "Found In" presentation in the work item layout to indicate what deliverable needs this task/contains this bug. Right now, everything goes into a single "backlog" and you can't tell without looking in the text what level of code they were running for example. However, I haven't found enough documentation to determine if adding these "releases" (let's say, V2, V3, V4, V5) would have any impacts on other things, like planning, routing of work items, etc.

Susan

2 answers



permanent link
Ralph Schoon (63.3k33646) | answered Jan 13 '11, 4:14 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Susan,

you should define the releases. The field is for the purpose you describe below. As far as I can tell there will be no impact on the way you work today, except you have additional information to use in queries etc.

Ralph


In a work item there is a "Release" object which is normally shown in the "Found In" presentation in the layouts. For our project, we have none defined, so all we get is "Unassigned".

I'd like to define "Releases" in my project to coincide with our deliverables and then use the "Found In" presentation in the work item layout to indicate what deliverable needs this task/contains this bug. Right now, everything goes into a single "backlog" and you can't tell without looking in the text what level of code they were running for example. However, I haven't found enough documentation to determine if adding these "releases" (let's say, V2, V3, V4, V5) would have any impacts on other things, like planning, routing of work items, etc.

Susan

permanent link
w h (191824) | answered Oct 04 '12, 10:18 a.m.

So is Found In mostly considered a metadata record? 

We're looking to create some new work items and cherry pick the relevant Agile attributes for our forms to ensure the work items integrate seamlessly with RTC and with CLM (RRC, RQM, Insight).  We have an existing Releases attribute that we source from a custom configuration UI, but are hesitant to pull out Found In because it has it's own designated UI in RTC, and is mentioned as a key word in CLM integration with RQM and Insight. 

Does anyone have any throughts or definitive guidance on this? Would be most appreciated! Thank you.

Your answer


Register or to post 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.