Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: TLP Admin
    • Labels:
      None

      Description

      Amber/Oltu currently has a Jira at https://issues.apache.org/jira/browse/AMBER

      may you rename to https://issues.apache.org/jira/browse/OLTU and issues should be sent to issues@oltu.apache.org please.

        Issue Links

          Activity

          Hide
          Simone Tripodi added a comment -
          thanks a lot for your help [~ipv6guru], very appreciated!
          Show
          Simone Tripodi added a comment - thanks a lot for your help [~ipv6guru], very appreciated!
          Hide
          Gavin added a comment -
          Done, now go to dev@ list. (remember to -allow from jira@apache.org)
          Show
          Gavin added a comment - Done, now go to dev@ list. (remember to -allow from jira@apache.org )
          Hide
          Simone Tripodi added a comment -
          Hi there [~pctony],

          We just realised that issues@oltu.apache.org mail address does not exist and we requested it by mistake - would it be possible, please, to hijack notifications to dev@oltu.apache.org?
          I haven't found, in the admin panel, how to set it up by myself, sorry for bugging!

          TIA, all the best
          Show
          Simone Tripodi added a comment - Hi there [~pctony], We just realised that issues@oltu.apache.org mail address does not exist and we requested it by mistake - would it be possible, please, to hijack notifications to dev@oltu.apache.org ? I haven't found, in the admin panel, how to set it up by myself, sorry for bugging! TIA, all the best
          Hide
          Simone Tripodi added a comment -
          Hi there [~cutting], looks like the bulk move I performed yesterday automagically configured the redirects, i.e. AMBER-1 redirects OLTU-35, so FWIW +1 to not update AMBER issues references.

          [~pctony] we are now ready, I already setup AMBER people, Brian went Emeritus during Incubation days and Jukka is not part (yet :P) of Oltu.

          Thanks for supervising!
          Show
          Simone Tripodi added a comment - Hi there [~cutting], looks like the bulk move I performed yesterday automagically configured the redirects, i.e. AMBER-1 redirects OLTU-35 , so FWIW +1 to not update AMBER issues references. [~pctony] we are now ready, I already setup AMBER people, Brian went Emeritus during Incubation days and Jukka is not part (yet :P) of Oltu. Thanks for supervising!
          Hide
          Antonio Sanso added a comment -
          [~cutting] exactly.
          We did the bulk move and worked great!
          Thanks a lot.
          I, hence resolve the issue.
          Show
          Antonio Sanso added a comment - [~cutting] exactly. We did the bulk move and worked great! Thanks a lot. I, hence resolve the issue.
          Hide
          Doug Cutting added a comment -
          Although AMBER-1 will not be OLTU-1, AMBER-1 will redirect to the corresponding OLTU-X issue, no? So references to AMBER issues need not be updated.
          Show
          Doug Cutting added a comment - Although AMBER-1 will not be OLTU-1 , AMBER-1 will redirect to the corresponding OLTU-X issue, no? So references to AMBER issues need not be updated.
          Hide
          Tony Stevenson added a comment -
          I have created the OLTU project, and added Simone, Brian, and Jukka as admins. Please feel free to move across your config, i.e. components etc. Please note if you proceed with a bulk move AMBER-1 will not be OLTU-1

          Let me know once you are ready, as you will need to modify the roles for the project to allow access etc.

          Show
          Tony Stevenson added a comment - I have created the OLTU project, and added Simone, Brian, and Jukka as admins. Please feel free to move across your config, i.e. components etc. Please note if you proceed with a bulk move AMBER-1 will not be OLTU-1 Let me know once you are ready, as you will need to modify the roles for the project to allow access etc.
          Hide
          Antonio Sanso added a comment -
          [~pctony] [~ipv6guru] I know you guys are pretty busy :) but it would be really nice if you could create the JIRA project for OLTU.

          We (Oltu team) we can take care of the actual migration if this is the blocker...
          Show
          Antonio Sanso added a comment - [~pctony] [~ipv6guru] I know you guys are pretty busy :) but it would be really nice if you could create the JIRA project for OLTU. We (Oltu team) we can take care of the actual migration if this is the blocker...
          Hide
          Antonio Sanso added a comment -
          hi guys any news :) ?
          Show
          Antonio Sanso added a comment - hi guys any news :) ?
          Hide
          Antonio Sanso added a comment -
          hi [~pctony] thanks for your comment.

          Please create the new OLTU project and we will take care to migrate it (even manually since there are not so many).

          Thanks

          Antonio
          Show
          Antonio Sanso added a comment - hi [~pctony] thanks for your comment. Please create the new OLTU project and we will take care to migrate it (even manually since there are not so many). Thanks Antonio
          Hide
          Tony Stevenson added a comment -
          Simone,

          This is far from a trivial task. It means manually creating a new JIRA project which in itself is trivial, but to move issues from AMBER to OLTU will mean you have to manually, by hand, re-create all the components, versions, labels, user permissions, workflows etc
          Only once this is done can you move issues from Amber to Oltu.

          Please note, that with the current version of JIRA AMBER-1 is not guaranteed to be OLTU-1 -- If this is an issue for you the only way to manage that is to move each issue one at a time.

          If we setup the JIRA project for you, can you set about creating all the things above?

          Show
          Tony Stevenson added a comment - Simone, This is far from a trivial task. It means manually creating a new JIRA project which in itself is trivial, but to move issues from AMBER to OLTU will mean you have to manually, by hand, re-create all the components, versions, labels, user permissions, workflows etc Only once this is done can you move issues from Amber to Oltu. Please note, that with the current version of JIRA AMBER-1 is not guaranteed to be OLTU-1 -- If this is an issue for you the only way to manage that is to move each issue one at a time. If we setup the JIRA project for you, can you set about creating all the things above?
          Hide
          Simone Tripodi added a comment -
          Thanks a lot in advance [~ipv6guru], that would be fine!
          Show
          Simone Tripodi added a comment - Thanks a lot in advance [~ipv6guru], that would be fine!
          Hide
          Gavin added a comment -
          [~asanso]

          Sorry for delay.

          We can not rename jira projectrs, what we would have to do is create a new Jira project and move all issues to that.

          Assuming no opposition to that method, I'll do that tomorrow.
          Show
          Gavin added a comment - [~asanso] Sorry for delay. We can not rename jira projectrs, what we would have to do is create a new Jira project and move all issues to that. Assuming no opposition to that method, I'll do that tomorrow.
          Hide
          Antonio Sanso added a comment -
          hi guys,

          any update :) ?
          Show
          Antonio Sanso added a comment - hi guys, any update :) ?

            People

            • Assignee:
              Unassigned
              Reporter:
              Antonio Sanso
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development