WorkItem granularity scope question
Hi,
I'd like to get some clarification on the scope of the workitems granularity.
When one creates a WI, it is filed against a Stream within a specified project area. Then one can add related artifacts under the form of a URI.
- How can one specified a deeper granularily; if I want to assign for instance a WI for a given Java file in a plugin project located in a component for a given stream?
- What about if I want to link a SCM artifact from a repository from within a WI (I could maybe add a related artifact link but I don't know of the URI artifact?
Could someone please clarify those 2 points?
Thank you in advance...
I'd like to get some clarification on the scope of the workitems granularity.
When one creates a WI, it is filed against a Stream within a specified project area. Then one can add related artifacts under the form of a URI.
- How can one specified a deeper granularily; if I want to assign for instance a WI for a given Java file in a plugin project located in a component for a given stream?
- What about if I want to link a SCM artifact from a repository from within a WI (I could maybe add a related artifact link but I don't know of the URI artifact?
Could someone please clarify those 2 points?
Thank you in advance...
2 answers
A workitem is not filed against a stream, it is filed against a
"category". In your project area, you define the mapping from a
category to a team area, which is what causes workitems to appear in the
plan for a given team area.
If you want to associate a versionable artifact with a work item, you
would obtain a URL for that versionable artifact (commonly, from the
Eclipse properties of that file), and store it as the value of a Related
Artifacts link.
I've submitted a couple of work items to make it easier to obtain that
URL (101251 and 101253). Also, work item 99555 requests the ability to
create a "direct" link from a work item to a versionable artifact, so
you don't have to obtain the URL first.
Please feel from to comment on any of these work items, to indicate
which if any would be important to you.
Cheers,
Geoff
eclipsetalk wrote:
"category". In your project area, you define the mapping from a
category to a team area, which is what causes workitems to appear in the
plan for a given team area.
If you want to associate a versionable artifact with a work item, you
would obtain a URL for that versionable artifact (commonly, from the
Eclipse properties of that file), and store it as the value of a Related
Artifacts link.
I've submitted a couple of work items to make it easier to obtain that
URL (101251 and 101253). Also, work item 99555 requests the ability to
create a "direct" link from a work item to a versionable artifact, so
you don't have to obtain the URL first.
Please feel from to comment on any of these work items, to indicate
which if any would be important to you.
Cheers,
Geoff
eclipsetalk wrote:
Hi,
I'd like to get some clarification on the scope of the workitems
granularity.
When one creates a WI, it is filed against a Stream within a specified
project area. Then one can add related artifacts under the form of a
URI.
- How can one specified a deeper granularily if I want to assign for
instance a WI for a given Java file in a project located in a
component for a given stream?
- What about if I want to link a SCM artifacts from a repository from
within a WI (I could maybe add a related artifacts but I don't know
of the URI artifact?
Could someone please clarify those 2 points?
Thank you in advance...