Re: How to set a default priority

This page has an answer to your question about a default value:

http://www.roundup-tracker.org/docs/design.html

Go to the 'Hyperdb Interface Specification' section and look for default_value. This is specified in the schema.py file when defining fields. In this case, use your favorite editor to edit schema.py. Look for 'issue =' (without quotes) and move down to where the priority field is defined. Change the definition of priority from Link('priority") to Link("priority", default_value=pri.lookup("urgent")).

I have never done this but perhaps one of the roundup experts can confirm this solution. The urgent priority lookup value is defined in initial_data.py.

Senior Computer Specialist, Lab Medicine
4th Floor, Pat Steel Building, currently WFH
Home: (253) 561-2509
Email: [email protected]

________________________________
From: R. Diez via Roundup-users <[email protected]>
Sent: Wednesday, April 22, 2020 2:29 AM
To: [email protected] <[email protected]>
Subject: [Roundup-users] How to set a default priority

Hi all:

I am evaluating the Roundup Issue Tracker. It has landed on my shortlist because it looks sensible, which is no small feat in this day and age of
garbage software.  8-)

I think the demo will be fine for a small business. It has everything you need really.

The only thing that bothers me is that the priority field is required when entering a new issue. I would like the priority to have a default value, so
that creating an issue requires one less mouse click. I am not sure I will be using it anyway.

I have looked around, but the answer to this simple question is not documented (or I have not found it yet).

I found file demo/html/issue.item.html , and this snippet inside it:

<tr>
  <th class="required" i18n:translate="">Priority</th>
  <td tal:content="structure context/priority/menu">priority</td>

I would have to change the way in which context/priority/menu generates the menu.

Or maybe there is some way to specify a default in the database for this field.

Please be gentle. I can do Perl, but no Python yet. ;-)

Now that I am here, I have another question. I wonder what would happen if people start attaching large files. Is there a way to list all issues with
big attachments, and maybe delete the files if they become too big?

This is similar to what happens with e-mail: you want to keep old e-mails, but not the huge attachments inside, or your mailbox size will sooner or
later become unmanageable.

Thanks in advance,
   rdiez


_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users