esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <>
Subject Re: Pool permissions can't be edited
Date Thu, 13 May 2010 07:51:45 GMT
Vassil is correct - when I changed the UI I split the pool selectbox and the
edit permissions area. Without the pool id, the scala logic doesn't work
anymore. There is also a bug in the Javascript for the dialog for adding a
user - I copied the code from the create a pool dialog and didn't change the
form name.

Ideally, the user would use the selectbox to select the pool to edit. This
pool would then be available / visible in the "add a user" dialog (@Vassil -
would "Edit" be a better title ?)

On Wed, May 12, 2010 at 10:41 PM, Vassil Dichev <> wrote:

> The pool page currently does not allow editing permissions for
> existing pools. First of all, the big "+Add"  button does not convey
> the right idea, because the action is setting a permission to a user,
> not necessarily adding a user to a pool. For instance, you can set
> permission Denied to a user, which can hardly be called "adding a
> user".
> More importantly, the pop-up box only has a text field for the user,
> not for the pool, so there's always an error message that the pool
> name is too short (I guess empty is too short).
> Is there a Jira item for this, or should i create one?
> Vassil

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message