incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #123: Check functionality of all screens with missing Products/Versions/Milestones/Components
Date Fri, 13 Jul 2012 11:11:26 GMT
#123: Check functionality of all screens with missing
Products/Versions/Milestones/Components
------------------------+-------------------------------------
  Reporter:  gjm        |      Owner:  nobody
      Type:  task       |     Status:  new
  Priority:  major      |  Milestone:  RC1 for initial release
 Component:  dashboard  |    Version:
Resolution:             |   Keywords:
------------------------+-------------------------------------

Comment (by gjm):

 Replying to [comment:3 jdreimann]:
 > 2. When a new component is added when there were none before, modifying
 a ticket allows you to select both the newly created component and the
 default Component 1, even if this doesn't exist. I suspect this is related
 to the issue I reported earlier (comment:1) but can't be sure myself.

 I noted that as I was writing comment:2 and, yes, it is essentially an
 aspect of that same behaviour. I do not think that we should lightly
 suggest that this is an error though. A ticket to change this would be an
 enhancement, not a bug fix.

 I have a few ideas of how this can be modified but perhaps the most
 promising would be to only allow a component to be deleted if it is empty
 (from web interface at least - I don't think we want to see errors if this
 is not adhered to in the database yet). This leaves the question of what
 to do if the admin wants to remove the last component of course.

 I will check on the widget error in a bit.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/123#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message