Re: issues with newly created status no longer show up in default, "your issues" views

----- Original Message -----
> From: "John P. Rouillard" <[email protected]>
> To: "Dan Tenenbaum" <[email protected]>
> Cc: "roundup-users" <[email protected]>
> Sent: Sunday, April 12, 2015 5:54:03 PM
> Subject: Re: [Roundup-users] issues with newly created status no longer show up in default, "your issues" views
> 
> 
> Hi Dan:
> 
> In message
> <[email protected]>,
> Dan Tenenbaum writes:
> >Hello, I created a new status:
> >
> >roundup-admin -i . create status order=11 name=foo
> >
> >Then I set an issue to have that status:
> >
> >roundup-admin -i . set issue558 status=foo
> >
> >After doing this, the issue stopped being visible in the default
> >view
> >of issues; in other words,>the root page of my tracker as viewed in
> >a
> >web browser. And though the issue is assigned to me, it stopped
> >being
> >visible in the "Your issues" view as well. If I change the issue's
> >status back to what it was before, it becomes visible again in both
> >views.
> 
> If I recall correctly both those searches are hard coded with a list
> of valid status values so that issues with resolved statuses aren't
> shown.
> 
> To get started, List the statuses and find the index number for the
> new status. You can use roundup-admin:
> 
> % roundup_admin -i /path/to/tracker
> Roundup 1.4.21 ready for input.
> Type "help" for help.
> 
> roundup> list status
>    1: new
>    2: open
>    3: stalled
>    4: hold
>    5: testing
>    6: resolved
>    7: duplicate
>    8: dead
>    9: delete
>   10: bring_out_your_dead
>   11: but_i'm_not_dead_yet
>   12: you_will_be_soon
>   13: yes_been_watching_mp
>   14: foo
> 
> Let's say it's 14. Then in the tracker directory edit:
> 
>   html/home.html
> 
> you should see something like:
> 
> <span tal:replace="structure python:db.issue.renderWith('index',
>     sort=[('-', 'activity')], group=[('+', 'priority')],
>     filter=['status'],
>     columns=['id','activity','title','creator','assignedto',
>     'status'],
>     filterspec={'status':['-1','1','2','3','4','5','6','7']})" />
> 
> add '14' to the filterspec so it reads:
> 
>      filterspec={'status':['-1','1','2','3','4','5','6','7','14']}
> 
> This should fix the default view of issues.
> 
> Now look at page.html, just before "Your Issues" there is a search
> that uses:
> 
>       'status': status_notresolved,
> 
> Searching from the top of page.html for status_notresolved we find:
> 
>   status_notresolved string:-1,1,2,3,4,5,6,7;
> 
> inside a tal:define. Change that to be
> 
>   status_notresolved string:-1,1,2,3,4,5,6,7,14;
> 
> (again assuming the index for your new status is 14).
> 
> I think that's all you need. You may have some other searches with
> hardcoded status lists that need fixing, but they should be fixable
> in the same way.
> 
> Good luck.
> 

It works!
Thanks,
Dan


> --
> 				-- rouilj
> John Rouillard
> ===========================================================================
> My employers don't acknowledge my existence much less my opinions.
> 

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF