Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Behind the Scenes
  3. Qt.io webservices
  4. Transferral to JIRA Cloud has caused SSO authentication to prevent me accessing my previous account.
Forum Updated to NodeBB v4.3 + New Features

Transferral to JIRA Cloud has caused SSO authentication to prevent me accessing my previous account.

Scheduled Pinned Locked Moved Solved Qt.io webservices
4 Posts 2 Posters 122 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • RokeJulianLockhartR Offline
    RokeJulianLockhartR Offline
    RokeJulianLockhart
    wrote last edited by
    #1
    Context

    After bypassing jira.atlassian.com/browse/ID-9038, then QTJIRA-416, I now see something very similar to moodle.org/mod/forum/discuss.php?d=469570&parent=1885343: when I access qt-project.atlassian.net/issues/?filter=-2, I don't see what issues/?jql=reporter%20%3D%20712020%3A7bee7586-ea5a-4787-a8f0-6ddbc4c60ce4 returns. Instead, I see issues/?jql=reporter%20%3D%2060ed8e7ff664300069c9cc37.

    Potential Solutions

    If anyone else is in this predicament, I believe that:

    • One can authenticate with their previous e-mail address, which shall cause the JIRA Server account that's been migrated to a JIRA Cloud account to become accessible. However, I leant that from the aforecited Moodle transfer, so I don't know whether it not being bound to your Qt SSO shall matter. I'll verify when I'm able to.

    • If not, I suppose that I need to ascertain where to file a ticket to have my JIRA tickets transferred to my new Atlassian account, that is bound to my Qt SSO.

    When using a forum, remember to tag the person you are responding to, in case they are not subscribed to the thread.

    aha_1980A 1 Reply Last reply
    0
    • aha_1980A aha_1980

      Hi @RokeJulianLockhart

      This mail arrived some hours ago:

      """
      Hi

      The Jira Open Source project migration was completed. All Jira services resume under https://qt-project.atlassian.net.

      You will need your Qt Account and Atlassian account credentials. Users with active edit/comment history should have received an email invitation from me via id.atlassian.net. Please check your inbox/spam. If not, simply sign up for an Atlassian account with the same email as your Qt Account.

      Please see https://wiki.qt.io/Jira_Cloud_migration for first details.

      For support requests please use one of the following channels:

      Jira Admin Support in Jira itself
      jira-admin@qt-project.org
      

      --
      Alex

      P.S. In anticipation of quite a few support requests, we will handle requests which are already covered by the above wiki with much lower priority. Therefore please check the wiki first before filing a request. We appreaciate your consideration.
      """

      I read the wiki page and then registered with my previous mail under https://qt-project.atlassian.net and everything works good so far. I see all my issues (created and assigned) so I'd say give it a try.

      Regards

      RokeJulianLockhartR Offline
      RokeJulianLockhartR Offline
      RokeJulianLockhart
      wrote last edited by RokeJulianLockhart
      #3

      @aha_1980, thanks. If you can replace that with the text/plain content of the .eml file, that might be more useful, since I'd have a better idea of who sent it.


      Otherwise, ⪆ #For_migrated_users at the cited wiki.qt.io/index.php?title=Jira_Cloud_migration&oldid=45055 appears to explain why I didn't see this:

      Note that not all accounts on bugreports.qt.io were migrated because Atlassian employs email filtering which prevents usage of certain email domains (e.g. one-time mailer domains).

      ...as if that's acceptable.

      Regardless, I attempted to add my Qt SSO e-mail address at id.atlassian.com/manage-profile/email#settings-new-email-field-uid10. However, it merely returned:

      Your email change request could not be processed because w3k98eqp@rokejulianlockhart.addy.io is already associated with another Atlassian account.

      Therefore, I've filed:

      1. my.qt.io/support/request/00785016

      2. qt-project.atlassian.net/browse/QTJIRA-417

      ...to have my tickets transferred from my old account to my new account.

      When using a forum, remember to tag the person you are responding to, in case they are not subscribed to the thread.

      1 Reply Last reply
      1
      • RokeJulianLockhartR RokeJulianLockhart
        Context

        After bypassing jira.atlassian.com/browse/ID-9038, then QTJIRA-416, I now see something very similar to moodle.org/mod/forum/discuss.php?d=469570&parent=1885343: when I access qt-project.atlassian.net/issues/?filter=-2, I don't see what issues/?jql=reporter%20%3D%20712020%3A7bee7586-ea5a-4787-a8f0-6ddbc4c60ce4 returns. Instead, I see issues/?jql=reporter%20%3D%2060ed8e7ff664300069c9cc37.

        Potential Solutions

        If anyone else is in this predicament, I believe that:

        • One can authenticate with their previous e-mail address, which shall cause the JIRA Server account that's been migrated to a JIRA Cloud account to become accessible. However, I leant that from the aforecited Moodle transfer, so I don't know whether it not being bound to your Qt SSO shall matter. I'll verify when I'm able to.

        • If not, I suppose that I need to ascertain where to file a ticket to have my JIRA tickets transferred to my new Atlassian account, that is bound to my Qt SSO.

        aha_1980A Offline
        aha_1980A Offline
        aha_1980
        Lifetime Qt Champion
        wrote last edited by
        #2

        Hi @RokeJulianLockhart

        This mail arrived some hours ago:

        """
        Hi

        The Jira Open Source project migration was completed. All Jira services resume under https://qt-project.atlassian.net.

        You will need your Qt Account and Atlassian account credentials. Users with active edit/comment history should have received an email invitation from me via id.atlassian.net. Please check your inbox/spam. If not, simply sign up for an Atlassian account with the same email as your Qt Account.

        Please see https://wiki.qt.io/Jira_Cloud_migration for first details.

        For support requests please use one of the following channels:

        Jira Admin Support in Jira itself
        jira-admin@qt-project.org
        

        --
        Alex

        P.S. In anticipation of quite a few support requests, we will handle requests which are already covered by the above wiki with much lower priority. Therefore please check the wiki first before filing a request. We appreaciate your consideration.
        """

        I read the wiki page and then registered with my previous mail under https://qt-project.atlassian.net and everything works good so far. I see all my issues (created and assigned) so I'd say give it a try.

        Regards

        Qt has to stay free or it will die.

        RokeJulianLockhartR 1 Reply Last reply
        1
        • aha_1980A aha_1980

          Hi @RokeJulianLockhart

          This mail arrived some hours ago:

          """
          Hi

          The Jira Open Source project migration was completed. All Jira services resume under https://qt-project.atlassian.net.

          You will need your Qt Account and Atlassian account credentials. Users with active edit/comment history should have received an email invitation from me via id.atlassian.net. Please check your inbox/spam. If not, simply sign up for an Atlassian account with the same email as your Qt Account.

          Please see https://wiki.qt.io/Jira_Cloud_migration for first details.

          For support requests please use one of the following channels:

          Jira Admin Support in Jira itself
          jira-admin@qt-project.org
          

          --
          Alex

          P.S. In anticipation of quite a few support requests, we will handle requests which are already covered by the above wiki with much lower priority. Therefore please check the wiki first before filing a request. We appreaciate your consideration.
          """

          I read the wiki page and then registered with my previous mail under https://qt-project.atlassian.net and everything works good so far. I see all my issues (created and assigned) so I'd say give it a try.

          Regards

          RokeJulianLockhartR Offline
          RokeJulianLockhartR Offline
          RokeJulianLockhart
          wrote last edited by RokeJulianLockhart
          #3

          @aha_1980, thanks. If you can replace that with the text/plain content of the .eml file, that might be more useful, since I'd have a better idea of who sent it.


          Otherwise, ⪆ #For_migrated_users at the cited wiki.qt.io/index.php?title=Jira_Cloud_migration&oldid=45055 appears to explain why I didn't see this:

          Note that not all accounts on bugreports.qt.io were migrated because Atlassian employs email filtering which prevents usage of certain email domains (e.g. one-time mailer domains).

          ...as if that's acceptable.

          Regardless, I attempted to add my Qt SSO e-mail address at id.atlassian.com/manage-profile/email#settings-new-email-field-uid10. However, it merely returned:

          Your email change request could not be processed because w3k98eqp@rokejulianlockhart.addy.io is already associated with another Atlassian account.

          Therefore, I've filed:

          1. my.qt.io/support/request/00785016

          2. qt-project.atlassian.net/browse/QTJIRA-417

          ...to have my tickets transferred from my old account to my new account.

          When using a forum, remember to tag the person you are responding to, in case they are not subscribed to the thread.

          1 Reply Last reply
          1
          • aha_1980A Offline
            aha_1980A Offline
            aha_1980
            Lifetime Qt Champion
            wrote last edited by aha_1980
            #4

            @RokeJulianLockhart

            For reference: This is the archived version of the mail I quoted in my post above.

            Regards.

            Qt has to stay free or it will die.

            1 Reply Last reply
            1
            • RokeJulianLockhartR RokeJulianLockhart has marked this topic as solved

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved