Work items
would like to see the following features\activities in your Bug Manager tool:
1. Quick search for a bug by bug ID 2. Advanced search for a bug by predefined criteria (text, bug's issuer etc') 3. Adding a comment with attaching a file to it 4. Duplicating a bug 5. Will there be a spell checker? 6. Is there an option to transform a bug to another entity? (for example a CR) 7. I would like to see how easy it is to produce a report for all bugs in a certain status that are related to a certain feature in the product. 8. Can a report be exported to excel? 9. Can the user choose to publish his report and allow all to view its' results? 10. I would like to see how easy is it to change\add a field in the bug form (from the administrator side |
6 answers
1. is available as 'Quick Search' in the status bar and the query editor (New > Work Item Query)
2. the query editor allows for complex queries (New > Work Item Query) 3. discussion and attachments are supported in the work item editor (New > Work Item or toolbar action) 4. see 'Duplicate' action in the context menu of work items 5. the work item editor uses Eclipse's spell checking facility (Preferences > Spelling) 6. yes, you can change the type of a work item and it will get the new type's additional attributes when saved 10. you add a new attribute to a work item type and a presentation to the editor layout in the process configuration, see https://jazz.net/learn/LearnItem.jsp?href=content/docs/work-items-cust/index.html for screenshots and documentation I'll leave 7-9 to someone from the Reports team who will be able to answer with more detail, Regards, Christof Jazz Work Item team ilazar wrote: would like to see the following features\activities in your Bug |
7. It depends what you mean by "report". If you just want a list of all
the bugs in a certain state, related to a certain component or team, that is possible already using work item queries; you can configure which columns are returned, and export the result as CSV if you want. If you want an over-time historical aggregated report, the reports component can do this, although our out-of-the-box reports probably aren't quite what you want so you'd have to write your own report using the BIRT report designer. 8. Reports produced by the reports component can be exported to Excel, with one current limitation: charts and other images do not appear in the excel document. However, tables are properly exported. This is currently a limitation of BIRT which they will be fixing in a future version. 9. Reports may be shared with the team, in which case they will show up under "Shared Reports" and can be viewed by others. Hope this helps. james Jazz Reports Team Lead Christof Marti wrote: 1. is available as 'Quick Search' in the status bar and the query editor |
|
We are now in BL 17
How we can take old versions files that is in Old Baseline 2 that have WI defect, Solved this defect , and deliver them to BL 2 and also to BL17 (our current BL) with out run over the cod Without run over our cod in BL 17? |
|
I will explain my Case:
I have Customer that used RTC 3.0 on VS 2010 He had One Project called G_Project with one Component called G_Comp with one Stream called G_Stream , He developed and create Baseline called REL 2 ,He Released is Product in REL 2 . Then he continue to developed, he is now in BL REL 17 at G_Comp, Is Customers found Work Item type Defect in this Baseline REL 2 , the asked him to solved this WI defect , Now what he had to do? My Solution is: I will Open New Repository Workspace Called Maintenance RW and i will take G_coMp with REL 2, But now i have problem were to Deliver the Stream Is on REL17 ? So if i will Deliver this resolved defect it will Run over on files that changed in REL 17, My suggestion that in first place i will create Maintenance Stream Called M_Stream that i will deliver this resolved , I need to deliver this resolved Defect to REL 2 and to REL 17 Without run over the Code, how i can deliver twice 1. deliver to REL 2 2. Deliver to REL 17 ? |
|
I have Customer that used RTC 3.0 on VS 2010
He had One Project called G_Project with one Component called G_Comp with one Stream called G_Stream , He developed and create Baseline called REL 2 ,He Released is Product in REL 2 . Then he continue to developed, he is now in BL REL 17 at G_Comp, Is Customers found Work Item type Defect in this Baseline REL 2 , the asked him to solved this WI defect , Now what he had to do? My Solution is: I will Open New Repository Workspace Called Maintenance RW and i will take G_Comp with REL 2, But now i have problem were to Deliver the Stream Is on REL17 ? So if i will Deliver this resolved defect it will Run over on files that changed in REL 17, My suggestion that in first place i will create Maintenance Stream Called M_Stream that i will deliver this resolved , I need to deliver this resolved Defect to REL 2 and to REL 17 Without run over the Code, how i can deliver twice 1. deliver to REL 2 2. Deliver to REL 17 ? |
|
I have Customer that used RTC 3.0 on VS 2010
He had One Project called G_Project with one Component called G_Comp with one Stream called G_Stream , He developed and create Baseline called REL 2 ,He Released is Product in REL 2 . Then he continue to developed, he is now in BL REL 17 at G_Comp, Is Customers found Work Item type Defect in this Baseline REL 2 , the asked him to solved this WI defect , Now what he had to do? My Solution is: I will Open New Repository Workspace Called Maintenance RW and i will take G_Comp with REL 2, But now i have problem were to Deliver the Stream Is on REL17 ? So if i will Deliver this resolved defect it will Run over on files that changed in REL 17, My suggestion that in first place i will create Maintenance Stream Called M_Stream that i will deliver this resolved , I need to deliver this resolved Defect to REL 2 and to REL 17 Without run over the Code, how i can deliver twice 1. deliver to REL 2 2. Deliver to REL 17 ? |
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.