You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/08/29 09:47:33 UTC

[jira] Closed: (INFRA-1339) 'New Jira Project' can not be assigned the 'Jira' Component.

     [ https://issues.apache.org/jira/browse/INFRA-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henri Yandell closed INFRA-1339.
--------------------------------

    Resolution: Fixed

I've added Component to that screen. It means the user (or the later editor) needs to choose the component, but not being able to set the component was irritating me too. Componentless issues are lost issues.

> 'New Jira Project' can not be assigned the 'Jira' Component.
> ------------------------------------------------------------
>
>                 Key: INFRA-1339
>                 URL: https://issues.apache.org/jira/browse/INFRA-1339
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: JIRA
>         Environment: Jira
>            Reporter: Gavin
>            Priority: Minor
>
> An example , Roller asking to have Jira project moved - this could get missed by our Jira admin if it is not placed in the 'Jira' component, but there is not option to create it there or to move it there. INFRA-1295 therefore is under 'no component' as a result. 
> Need to add this option when someone creates/edits 'New Jira Project' .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.