Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2471

Test our Loraine Lab Jira following migration to new host and upgrade to Jira v8

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Chester has created a clone of our current Jira server and upgraded it to Jira version 8.

      For this task, please test this Jira 8 instance to ensure proper behavior.

      Please check that:

      • Attachment links for attachments added after 2017 are available
      • Tickets can be moved from column to column as expected
      • You are able to log in using your current Jira credentials
      • Links between issues function properly
      • Search is working as expected
      • Check that emailing is working properly

      Also, please log in as an admin user and check that:

      • You can add a new user
      • You can modify an existing user

      Please also think of additional things to test and add them here.

      Make note of any problems.

      JIRA TEST LINK: https://jiratest.bioviz.org/secure/RapidBoard.jspa?rapidView=11

      Current JIRA is running on below specifications
      AMI: ami-6869aa05
      Instance Type: t2.large
      Disk: 100 GB

      Test JIRA configured is running on below specifications
      AMI: ami-09d95fab7fff3776c
      Instance Type: m5a.large
      Disk: 8GB

        Attachments

        1. AWS JIRA Recommendations.xlsx
          9 kB
        2. Error.JPG
          Error.JPG
          257 kB
        3. IGB Testing.JPG
          IGB Testing.JPG
          81 kB
        4. Release Testing - 1.JPG
          Release Testing - 1.JPG
          70 kB
        5. Test Board.JPG
          Test Board.JPG
          80 kB

          Activity

          Hide
          cdias1 Chester Dias (Inactive) added a comment - - edited

          I was able to login with my existing credentials.

          Also check out this plugin
          https://marketplace.atlassian.com/apps/1220209/issue-checklist-free?hosting=cloud&tab=overview

          Looks like this is not available
          Cc: [~aloraine]

          Show
          cdias1 Chester Dias (Inactive) added a comment - - edited I was able to login with my existing credentials. Also check out this plugin https://marketplace.atlassian.com/apps/1220209/issue-checklist-free?hosting=cloud&tab=overview Looks like this is not available Cc: [~aloraine]
          Hide
          shamika Shamika Gajanan Kulkarni (Inactive) added a comment -

          I and Prutha Kulkarni worked on this ticket to check the functioning of Jira following migration.
          Following are our observations:
          1) Attachments to tickets after 2017 are available and can be downloaded if necessary.
          2) Tickets can be moved from column to column as expected and can be updated. Attachments can be added to tickets.
          3) Jira credentials can be used to login
          4) Issues can be linked and the link functions properly.
          5) Search functions properly and filters work as expected.
          6) Emails are received for tickets being watched or assigned to.

          The following observations are made as well:
          1) New tickets can be created in any epic without facing any errors.
          2) New boards can be created and worked with.
          3) When we checked the configurations for existing boards on Jira (IGB, Release-testing), an error message is being displayed at the bottom for every option (like General, Columns, Swimlanes, Quick filters, Card Layout, Issue Detail View, etc.) but this message is not displayed for the board we created for testing (Named Test-Board). Please refer the screenshots attached to this ticket, to view the error message displayed.

          Show
          shamika Shamika Gajanan Kulkarni (Inactive) added a comment - I and Prutha Kulkarni worked on this ticket to check the functioning of Jira following migration. Following are our observations: 1) Attachments to tickets after 2017 are available and can be downloaded if necessary. 2) Tickets can be moved from column to column as expected and can be updated. Attachments can be added to tickets. 3) Jira credentials can be used to login 4) Issues can be linked and the link functions properly. 5) Search functions properly and filters work as expected. 6) Emails are received for tickets being watched or assigned to. The following observations are made as well: 1) New tickets can be created in any epic without facing any errors. 2) New boards can be created and worked with. 3) When we checked the configurations for existing boards on Jira (IGB, Release-testing), an error message is being displayed at the bottom for every option (like General, Columns, Swimlanes, Quick filters, Card Layout, Issue Detail View, etc.) but this message is not displayed for the board we created for testing (Named Test-Board). Please refer the screenshots attached to this ticket, to view the error message displayed.
          Hide
          cdias1 Chester Dias (Inactive) added a comment -

          Admin testing
          1. I tried modifying the JIRA user groups to grant my personal account higher privs, that seems to work.
          2. Also tried switching Transition states order like moving "IN PROGRESS" sections location to "NEEDS 1ST LEVEL REVIEW" locations. That seems to work.
          Shamika Gajanan Kulkarni and Prutha Kulkarni The error you have reported I believe is because your accounts are not administrator accounts(Configure of boards in an admin priv). I tried the same with admin account, didn't seem to get the error. Looks like we are good on that error.

          Cc: [~aloraine]

          Show
          cdias1 Chester Dias (Inactive) added a comment - Admin testing 1. I tried modifying the JIRA user groups to grant my personal account higher privs, that seems to work. 2. Also tried switching Transition states order like moving "IN PROGRESS" sections location to "NEEDS 1ST LEVEL REVIEW" locations. That seems to work. Shamika Gajanan Kulkarni and Prutha Kulkarni The error you have reported I believe is because your accounts are not administrator accounts(Configure of boards in an admin priv). I tried the same with admin account, didn't seem to get the error. Looks like we are good on that error. Cc: [~aloraine]
          Hide
          cdias1 Chester Dias (Inactive) added a comment - - edited

          After reading through the JIRA suggestions and running some time analysis on the type of instances used currently for existing workload and test instance performance.
          Jira recommends using m series instances for database and c series for JIRA server.

          I suggest below hardware configuration
          Instance Type: c5n.large or higher
          Disk size(EBS Volume): 15GB or higher
          Cost: $0.108 per Hour (slightly more expensive than our existing setup but we can get cost-benefit on the reserved instances )

          Cost reference: https://aws.amazon.com/ec2/pricing/on-demand/
          JIRA Infrastructure recommendation References: https://confluence.atlassian.com/enterprise/infrastructure-recommendations-for-enterprise-jira-instances-on-aws-969532459.html

          Note: Reserved instance costing is much lower than on-demand costing.
          Attached: Price and hardware comparison of 3 best instance types for our usage.

          Cc: [~aloraine]

          Show
          cdias1 Chester Dias (Inactive) added a comment - - edited After reading through the JIRA suggestions and running some time analysis on the type of instances used currently for existing workload and test instance performance. Jira recommends using m series instances for database and c series for JIRA server. I suggest below hardware configuration Instance Type: c5n.large or higher Disk size(EBS Volume): 15GB or higher Cost: $0.108 per Hour (slightly more expensive than our existing setup but we can get cost-benefit on the reserved instances ) Cost reference: https://aws.amazon.com/ec2/pricing/on-demand/ JIRA Infrastructure recommendation References: https://confluence.atlassian.com/enterprise/infrastructure-recommendations-for-enterprise-jira-instances-on-aws-969532459.html Note: Reserved instance costing is much lower than on-demand costing. Attached: Price and hardware comparison of 3 best instance types for our usage. Cc: [~aloraine]
          Hide
          ann.loraine Ann Loraine added a comment -

          Next step will be to run the migration playbooks in Loraine Lab account. Moving to Closed.

          Show
          ann.loraine Ann Loraine added a comment - Next step will be to run the migration playbooks in Loraine Lab account. Moving to Closed.

            People

            • Assignee:
              Unassigned
              Reporter:
              ann.loraine Ann Loraine
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: