Ticket #997 (closed planned_task: obsolete)
ANNOTATIONS_STICKIES_R0
| Reported by: | Astea | Owned by: | mitex |
|---|---|---|---|
| Priority: | 3 | Milestone: | M04_PRE4 |
| Component: | DOMAIN_ELEMENTS | Version: | 2.0 |
| Keywords: | Cc: | ||
| Category: | EXTRA | Effort: | 1 |
| Importance: | 0 | Ticket_group: | GROUP_ANNOTATIONS_R0 |
| Estimated Number of Hours: | Add Hours to Ticket: | ||
| Billable?: | Total Hours: | ||
| Analysis_owners: | mitex | Design_owners: | milo, mitex |
| Imp._owners: | mitex | Test_owners: | |
| Analysis_reviewers: | pap | Changelog: | |
| Design_reviewers: | meddle | Imp._reviewers: | meddle |
| Test_reviewers: | Analysis_score: | 3 | |
| Design_score: | 3 | Imp._score: | 3 |
| Test_score: | 0 |
Description
wiki page: ANNOTATIONS_STICKIES_R0 - effort: 1d
Change History
comment:1 Changed 16 years ago by mitex
- Status changed from new to s1a_analysis_started
- Analysis_score set to 0
- Test_score set to 0
- Design_score set to 0
- Owner changed from Astea to mitex
- Imp._score set to 0
- Analysis_owners set to mitex
comment:2 Changed 16 years ago by mitex
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:3 Changed 16 years ago by deyan
I think the sections are little messed up. Task requirements section describes stickies behavior, which is part of the overview. Implementation idea looks like task requirements. Also, you may extend the stickies behavior with something like "are you sure you want to delete this sticky" should be shown when sticky has something written in it.
comment:5 Changed 16 years ago by deyan
- Analysis_reviewers set to pap
- Analysis_score changed from 0 to 3
Batch update from file query.csv
comment:6 Changed 16 years ago by deyan
- Design_owners set to milo, mitex
- Design_score changed from 0 to 3
- Design_reviewers set to meddle
- Imp._owners set to mitex
Batch update from file import.csv
Note: See
TracTickets for help on using
tickets.
