Create Ticket
Warning Can't synchronize with repository "(default)" (/x1/svn/asf/bloodhound does not appear to be a Subversion repository.). Look in the Trac log for more information.

Reporter:
gjm  
Opened:
Type:
task  
Status:
new  
Priority:
major  
Milestone:
Component:
Version:
 
Description

This seems to be easy to forget so I thought I would turn this into a task for someone to make sure there are no glaring errors. Test views to check that they work properly when we have:

  • No Products defined
  • No Versions defined
  • No Milestones defined
  • No Components defined

This will be worth automating but neither should it hurt to look over manually.

Cc:
 

Change History

jdreimann

I've removed all Products / Versions / Milestones / Components from my local installation and everything seemed to work fine. For example, when there was no component to select, the drop down field just wasn't displayed in the various locations (like Quick Ticket and the Ticket view screen).

The only bit of funkiness I found was that when viewing any reports that showed a Components column, all tickets still showed as tagged with Component 1 if they were created before I removed the component. On the ticket pages themselves this was not showing.

Functionally not a problem, just a bit curious, and I would assume this relates to how tickets are being disassociated with deleted component types (or rather, a lack of disassociation). This may matter for some very specific cases, such as exporting ticket information.

gjm

Yes, there is some interesting behaviour around that. If components exist then it is not possible to create a ticket without a component for instance. You could argue that deletion of a component is really a closure of it while there are tickets with that as an attribute.

If you are missing all components though you have the additional interesting feature that existing reports are the only place that the component will be visible.

5 years ago

comment:3  

Follow-up:

jdreimann

I found two errors:

  1. With no versions defined, the widget showing versions on a Product page throws an exception:
Widget error    
Error  Exception raised while rendering widget. Contact your administrator for further details.

Widget name: TicketFieldValues
Exception type: InvalidWidgetArgument
Log entry ID: 9e082091-2d20-47c0-a5b5-ee9a1df7b87c
  1. 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.
5 years ago

comment:4  

In reply to: ↑ 3

gjm

Replying to jdreimann:

  1. 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.

gjm

Raised #136 to deal with the widget error found by jdreimann in comment:3

jdreimann

  • Keywords starter added
Note: See TracTickets for help on using tickets.

Activity

  

Warning   No events reported for task: Check functionality of all screens with missing ... (new) in the last 30 days since May 23, 2017. This may happen if system is not configured correctly. Please contact your administrator if you think this is the case.