You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2012/06/26 23:54:43 UTC
[jira] [Created] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Sebb created INFRA-4970:
---------------------------
Summary: Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
Key: INFRA-4970
URL: https://issues.apache.org/jira/browse/INFRA-4970
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: JIRA
Reporter: Sebb
3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403066#comment-13403066 ]
Sebb commented on INFRA-4970:
-----------------------------
OK, thanks.
Will do.
> Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
> ----------------------------------------------------------------------
>
> Key: INFRA-4970
> URL: https://issues.apache.org/jira/browse/INFRA-4970
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Sebb
>
> 3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
> These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401817#comment-13401817 ]
#asfinfra IRC Bot commented on INFRA-4970:
------------------------------------------
<gmcdonald> I've made you admin on there sebb so feel free to move those issues then let me know when done so I can make it read only
> Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
> ----------------------------------------------------------------------
>
> Key: INFRA-4970
> URL: https://issues.apache.org/jira/browse/INFRA-4970
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Sebb
>
> 3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
> These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403043#comment-13403043 ]
Sebb commented on INFRA-4970:
-----------------------------
Thanks, they have been moved by someone else.
It's now just a question of whether it's better to make SANSELAN read-only or delete it entirely.
I think it would be better as read-only, at least initially, so users can be redirected - the summary page already documents the rename.
> Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
> ----------------------------------------------------------------------
>
> Key: INFRA-4970
> URL: https://issues.apache.org/jira/browse/INFRA-4970
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Sebb
> Assignee: Gavin
>
> 3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
> These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401806#comment-13401806 ]
Sebb commented on INFRA-4970:
-----------------------------
I'm sure we don't still want SANSELAN, but I'll ask.
However, we do want the 3 new issues, can you move them to IMAGING?
I'm normally able to Admin commons issues, but edit and bulk move are not available to me.
> Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
> ----------------------------------------------------------------------
>
> Key: INFRA-4970
> URL: https://issues.apache.org/jira/browse/INFRA-4970
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Sebb
>
> 3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
> These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin reassigned INFRA-4970:
----------------------------
Assignee: Gavin
> Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
> ----------------------------------------------------------------------
>
> Key: INFRA-4970
> URL: https://issues.apache.org/jira/browse/INFRA-4970
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Sebb
> Assignee: Gavin
>
> 3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
> These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401752#comment-13401752 ]
Gavin commented on INFRA-4970:
------------------------------
Sorry, Infra did not rename this project, but I see what happened.
Someone created a new Jira project call IMAGING and then just 'moved' the issues fr om SANSELAN to it. They then removed all permissions for commons folks, whilst create issues etc is still possible. The SANSELAN project is still usable so whomever did the rename/move did not finish their job off properly by removing it.
Please discuss with the community then get back to me and say 'yes' we want the removal of the SANSELAN jira project.
> Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
> ----------------------------------------------------------------------
>
> Key: INFRA-4970
> URL: https://issues.apache.org/jira/browse/INFRA-4970
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Sebb
>
> 3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
> These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4970) Commons SANSELAN JIRA has 3 new
issues, but it was renamed as IMAGING?
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed INFRA-4970.
------------------------
Resolution: Fixed
Assignee: (was: Gavin)
OK, I've made the project read only, removed all other permissions and also removed the Notifcation Scheme.
There can be no alterations made now. Let us know under a new issue when you want it deleted altogether.
> Commons SANSELAN JIRA has 3 new issues, but it was renamed as IMAGING?
> ----------------------------------------------------------------------
>
> Key: INFRA-4970
> URL: https://issues.apache.org/jira/browse/INFRA-4970
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Sebb
>
> 3 new issues were raised under the SANSELAN tag. This should not be possible, as SANSELAN was renamed as IMAGING.
> These issues have numbers which follow on from the last IMAGING number, but the issues are in a strange state - for example there is no Edit button.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira