TWiki> Bugs Web>CurrentState (16 Feb 2007, TWikiGuest)EditAttach

Current State

Id Summary Applies To Priority Current State Last Edit Waiting For
Item26 Crawler sometimes finishes but does not terminate crawler Normal Confirmed 09 May 2008 - 16:19 KoenMartens
Item43 qi does not finish frontend Urgent Closed 09 May 2008 - 14:04  
Item6 Yang crashing regularly crawler Normal Being Worked On 09 May 2008 - 13:27  
Item1 Crawl "finished" but not displayed anywhere on issuecrawler.net frontend Urgent Being Worked On 08 May 2008 - 16:53 ErikBorra
Item44 crawl within a set of site, when all links of each site in the set found, see if they interlink. crawler Normal New 07 May 2008 - 15:16  
Item42 analyse errors from crawls frontend Urgent New 04 May 2008 - 10:56  
Item41 checkForPublishedCrawls frontend Urgent New 04 May 2008 - 10:54  
Item40 cbsd beter als crawler uit gaat crawler Urgent New 04 May 2008 - 10:23 KoenMartens
Item39 foutcondities van crawler worden niet goed aan de frontend doorgegeven worden crawler Normal New 04 May 2008 - 10:23  
Item38 increase allowed page size (links pages can be huge) crawler Normal New 04 May 2008 - 10:22  
Item37 name column in im_site is leeg crawler Enhancement New 04 May 2008 - 10:21  
Item36 Sometimes lost temp data when advanced setting tie specifity is used frontend Enhancement New 18 Apr 2008 - 13:14  
Item35 Consistent naming: make sure all xml + log files have network id in their filename frontend Normal New 14 Apr 2008 - 13:34  
Item16 Validity: crawl record; show effects of ceilings frontend Normal New 14 Apr 2008 - 13:31  
Item34 Lost temp data visualisation Normal New 13 Apr 2008 - 18:14  
Item13 Crawl completion is too slow, clogging up the queue crawler Urgent Closed 10 Apr 2008 - 08:16  
Item33 rss does not update anymore frontend Urgent New 10 Apr 2008 - 07:49 ErikBorra
Item32 delete map does not redirect to archive, import rendering.pages failed frontend Urgent New 10 Apr 2008 - 07:48 ErikBorra
Item27 Login system tools Urgent Being Worked On 09 Apr 2008 - 17:09 KoenMartens
Item31 Remote crawlers require more reliable publishing mechanism crawler Low Confirmed 09 Apr 2008 - 15:11  
Item29 Third crawler frontend Enhancement Closed 09 Apr 2008 - 15:09  
Item19 Optimize harvester to remove duplicates frontend Enhancement Closed 09 Apr 2008 - 13:03 ErikBorra
Item30 less nodes but more labels in clusermap advanced settings frontend Normal New 01 Apr 2008 - 16:10  
Item28 Prioritize Scheduled Crawls crawler Urgent Closed 01 Apr 2008 - 13:21  
Item25 advanced network rendering + saving / exporting frontend Urgent Closed 01 Apr 2008 - 13:01 ErikBorra
Item0 Test of the bug tracker frontend Normal Closed 01 Apr 2008 - 08:53  
Item15 Character encoding crawler Urgent New 01 Apr 2008 - 08:51 KoenMartens
Item21 Live view, when exiting, etc. ideally show timestamps. frontend Enhancement Closed 01 Apr 2008 - 08:50  
Item24 Some links in the svg have issuecrawler.net/svg2/h as href frontend Urgent New 11 Mar 2008 - 09:33  
Item9 MySQL? database collects dust over time, slowing down map generation visualisation Normal Closed 06 Mar 2008 - 07:47  
Item5 SVG does not display in native firefox SVG visualisation Urgent Closed 05 Mar 2008 - 12:20 ErikBorra
Item23 SVG reciprocal links visualisation Enhancement New 04 Mar 2008 - 13:28  
Item3 Enable circle map view again visualisation Enhancement Being Worked On 04 Mar 2008 - 12:50 ErikBorra
Item14 Circle Map visualisation Urgent Being Worked On 04 Mar 2008 - 12:49 ErikBorra
Item10 SVG rendering module can not handle simultaneous renderings per user frontend Normal Being Worked On 04 Mar 2008 - 12:39 ErikBorra
Item12 Server time-outs on svg load / session_id issues / pregenerating clusters in mysql visualisation Urgent New 04 Mar 2008 - 10:57  
Item22 Websphinx code is old crawler Normal Waiting for Feedback 04 Mar 2008 - 10:37 KoenMartens
Item20 Explore shadow crawl after all iterations have completed. crawler Low New 28 Feb 2008 - 20:26  
Item18 Edit schedule doesn't work frontend Normal New 28 Feb 2008 - 15:47  
Item17 Fixed colours and placement of nodes for crawls in a schedule visualisation Normal New 28 Feb 2008 - 15:44  
Item11 duplicate key violates unique constraint "crawled_urls_pkey" crawler Normal New 27 Jan 2008 - 21:23  
Item4 Problems with xml files frontend Normal Waiting for Feedback 12 Oct 2007 - 12:22  
ItemAUTOINC1 Issuegeographer not processing new requests frontend Urgent Closed 12 Oct 2007 - 12:21  
Item8 Issuegeographer bug when -1 appears in fields visualisation Urgent New 25 Sep 2007 - 13:57  
Item7 Add export to GraphML frontend Enhancement New 14 Sep 2007 - 09:48  
Item2 Map conversion crops image for bitmap formats visualisation Urgent Closed 28 Aug 2007 - 13:44  
    crawler: 14
frontend: 21
tools: 1
visualisation: 10 		Enhancement: 8
Low: 2
Normal: 17
Urgent: 19 		Being Worked On: 6
Closed: 12
Confirmed: 2
New: 24
Waiting for Feedback: 2 		   
  • CurrentState : New|Waiting for Feedback|Confirmed|Being Worked On|Waiting for Release|Closed|No Action Required
  • Summary : .*
  • AppliesTo : .*
  • WaitingFor : .*
  • Priority : .*
  • ReportedBy : .*

Current State

  • New the issue has just been found, and hasn't been analysed yet, or there is new data about an existing issue.
  • Waiting for feedback the report was insufficient to analyse the issue, and more feedback is needed from the person named in the "Waiting For" field. Once the reporter has added feedback they should flip the state back to "New". If feedback is not received within 30 days, the issue will be discarded.
  • Confirmed the issue has been analysed, and the priority has been confirmed (or changed) by a developer. The item can henceforth be classified regarding release blocking status etc. Someone needs to pick it up and fix it.
  • Being Worked On the issue has been analysed, and is being worked on by the developer named inthe "Waiting For" field.
  • Waiting for release the issue reported has been fixed and is queued for release. See the TargetRelease field to see whether it is queued for the next patch, minor, or major release. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why.
  • Closed the issue has been fixed to the satisfaction of the fixer, and has been through the "Waiting for release" state, and is now released to end users. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why. Note that bugs reported against new code (code that has not been released yet) or Extensions (Plugins etc) may jump straight to "Closed" without going through "Waiting for Release" first.
  • Deferred the issue will not be fixed for the release currently being worked on. The text should explain why.
  • No Action Required the issue was already fixed, or it's a duplicate, or a RTFM, or could not be reproduced and feedback was never received.

Please make sure there is an entry in the details explaining any state change.

Name Type ToolTip
New option  
Waiting for Feedback option  
Confirmed option  
Being Worked On option  
Waiting for Release option  
Closed option  
No Action Required option  
Edit | Attach | Print version | History: r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r1 - 16 Feb 2007 - 00:23:35 - TWikiGuest

 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback