Opened on 11/21/14 at 03:13:07
Closed on 01/19/23 at 14:31:05
#2196 closed infra (worksforme)
Too many ticket components
Reported by: | Gedare Bloom | Owned by: | Needs Funding |
---|---|---|---|
Priority: | normal | Milestone: | Indefinite |
Component: | admin | Version: | 4.11 |
Severity: | normal | Keywords: | tickets, migration |
Cc: | Chris Johns, Joel Sherrill | Blocked By: | |
Blocking: |
Description
There are 32 Component choices in the ticket system. We need to reduce the variety to make creating tickets simpler.
Change History (8)
comment:1 Changed on 11/21/14 at 03:19:37 by Gedare Bloom
comment:2 Changed on 12/07/14 at 22:30:35 by Amar Takhar
Keywords: | migration added |
---|
comment:3 Changed on 12/19/14 at 04:42:21 by Gedare Bloom
Component: | Ada → admin |
---|---|
Milestone: | 4.11 → 4.11.1 |
Priority: | highest → normal |
Type: | defect → infra |
comment:4 Changed on 01/26/17 at 07:16:00 by Sebastian Huber
Milestone: | 4.11.1 → 4.11.2 |
---|
comment:5 Changed on 02/15/17 at 13:37:51 by Sebastian Huber
Milestone: | 4.11.2 → Indefinite |
---|---|
Owner: | changed from Amar Takhar to Needs Funding |
Status: | new → assigned |
comment:7 Changed on 02/16/20 at 04:25:03 by Gedare Bloom
On one hand, I think it is still valid to complain about the complexity of the ticket "Components" from a usability perspective, especially considering we don't use that feature to direct ticket assignment to the right maintainer.
On the other hand, it is probably not a big enough problem to really care about, since no one bothers to change it in 5 years.
comment:8 Changed on 01/19/23 at 14:31:05 by Amar Takhar
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
We are at 8 years now and it's still not changed. :) I think we're good!
Note: See
TracTickets for help on using
tickets.
Fixing this problem might be easier if it coincides with updating the rtems.git repository layout, as that should simplify some of the logical components within the tree.
Then, outside the tree, we should stick to more abstract component names that are not tied to particular software products, e.g.
And then there should be components for the associated RTEMS Project products with publicly-supported repositories, such as
While we may end up with still over a dozen components, they will be logically associated with a repository or a project service / dependency.