Changing Alias of Requirement prevents creation of new requirements

[Lorin Hochstein]

In our setup, we changed the alias of "Requirement" to "Project", but otherwise didn't change the ticket type. Once we changed this alias, we were no longer able to create new Project tickets, we would get this error:

Warning: No permission to create or edit a project.

I tracked this error message down to this method in agilo/ticket/web_ui.py (line 530)

    def validate_ticket(self, req, ticket):
        if not ticket.exists:
            typename = ticket.get_type()
            permission_name = 'CREATE_%s' % typename.upper()
            permission_name = getattr(Action, permission_name, permission_name)
            if permission_name not in req.perm(ticket.resource):
                msg = _("No permission to create or edit a %s.")  % typename
                return [(None, msg)]

Apparently, it was returning "project" for typename. I thought that it would have returned the field shown as "Type" on the Manage Types page (which was still "requirement"), rather than "project", which was just defined as the alias.

We're running Agilo (open source) 0.9.7.

Take care,

Lorin Hochstein

[Stefano Rago]

Hi Lorin,

Renaming is definitely an area that needs improvement. We are aware of this kind of issue and have plans to fix it.

Thanks for pointing it out.

Cheers

Stefano Rago