Re: prevent changing Status for new issues

On 10/04/2014 01:43 PM, Stuart McGraw wrote:
> On 10/04/2014 12:10 PM, Stuart McGraw wrote:
>>[...]
>> Yet users with only User role can still set status and resolution to
>> be anything when creating a new issue. 

I added the following to issue.item.html:

  <tr>
  <td colspan="5">
   context/status/is_edit_ok: <span tal:replace="python: repr(context.status.is_edit_ok())"/><br>
   user: <span tal:content="python:request.user.username">xxxx</span><br>
   user.hasPermission('Create', 'status'): <span tal:replace="python:repr(request.user.hasPermission('Create', 'status'))"/><br>
   user.hasPermission('Edit', 'status'): <span tal:replace="python:repr(request.user.hasPermission('Edit', 'status'))"/>
  </td>
  </tr>

and got the following output when creating a new issue when
logged in as user "user", who's only role membership is "User":

  context/status/is_edit_ok: 1
  user: user
  user.hasPermission('Create', 'status'): 0
  user.hasPermission('Edit', 'status'): 0

I clearly am badly misunderstanding something.  How can I not
have either Edit ot Create privilege and yet have is_edit_ok be
true?
	

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk