#2196 assigned infra

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 (7)

comment:1 Changed on Nov 21, 2014 at 3:19:37 AM by Gedare Bloom

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.

  • admin
  • build system
  • compilers

And then there should be components for the associated RTEMS Project products with publicly-supported repositories, such as

  • RTEMS Source Builder
  • RTEMS Testing
  • RTEMS Examples (easier if we merge all example repos together)
  • RTEMS Scheduler Simulator
  • etc.

While we may end up with still over a dozen components, they will be logically associated with a repository or a project service / dependency.

comment:2 Changed on Dec 7, 2014 at 10:30:35 PM by Amar Takhar

Keywords: migration added

comment:3 Changed on Dec 19, 2014 at 4:42:21 AM by Gedare Bloom

Component: Adaadmin
Milestone: 4.114.11.1
Priority: highestnormal
Type: defectinfra

comment:4 Changed on Jan 26, 2017 at 7:16:00 AM by Sebastian Huber

Milestone: 4.11.14.11.2

comment:5 Changed on Feb 15, 2017 at 1:37:51 PM by Sebastian Huber

Milestone: 4.11.2Indefinite
Owner: changed from Amar Takhar to Needs Funding
Status: newassigned

comment:6 Changed on Jan 29, 2020 at 11:18:47 PM by Chris Johns

Is this ticket valid? Can it be closed?

comment:7 Changed on Feb 16, 2020 at 4:25:03 AM 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.

Note: See TracTickets for help on using tickets.