www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7068) Create Issue for HCATALOG actually creates issue in different project
Date Wed, 04 Dec 2013 02:38:35 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838522#comment-13838522

Gavin commented on INFRA-7068:

So someone has edited the HCatalog permissions scheme so that nobody can create issues. I'm
assuming that's someone trying to make the jira project read only.
Infra has not had an issue created asking for the jira project to be made read only nor has
it been told of the amalgamation into Hive (nor has it been asked to merge the Jira tickets
into Hive, ) etc etc ..

I've changed the scheme to that of a read only one. I've updated the URL and Description of
the Jira project.

> Create Issue for HCATALOG actually creates issue in different project
> ---------------------------------------------------------------------
>                 Key: INFRA-7068
>                 URL: https://issues.apache.org/jira/browse/INFRA-7068
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA
>         Environment: https://issues.apache.org/jira/browse/HCATALOG
>            Reporter: Sebb
>            Assignee: Gavin
> Navigate to
> https://issues.apache.org/jira/browse/HCATALOG
> Click "Create Issue"
> The project is changed to whatever was last selected (as far as I can tell).
> Not sure if this is a JIRA bug or a JIRA configuration issue, but it's very confusing.
> AIUI HCATALOG has been merged into Hive, so it would be better if the project changed
to HIVE rather than whatever was last used.

This message was sent by Atlassian JIRA

View raw message