Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4199

Jira Align is incorrectly saving Capability Links into tblAgileLinks with ObjectType = 1

    XMLWordPrintable

Details

    • 1
    • Severity 3 - Minor
    • No

    Description

      Issue Summary

      Jira Align is saving Capability Links into tblAgileLinks with ObjectType = 1 instead of 43.


      Jira Align stores work item links into the tblAgileLinks and assigns an ObjectType id based on the type of work item link that it is.

      When Enterprise Insights calls that data using the script GET_ExternalReference.sql it is looking for ObjectType 43 for Capabilities

      SELECT
      	  ER.UniqueID AS [External Reference ID]
      	, ER.LinkName as [External Reference Name]
      	, ER.Link AS [External Reference Value]
      	, CASE ER.ObjectType
      		WHEN 1 THEN N'Epic'
      		WHEN 43 THEN N'Capability'
      		WHEN 2 THEN N'Feature'
      		WHEN 3 THEN N'Story'
      		WHEN 44 THEN N'Objective'
      		WHEN 5 THEN N'Risk'
      		WHEN 64 THEN N'Dependency'
      		ELSE N'Unknown'
      	  END AS [Object Type]
      

      However, when the data is stored into the Jira Align database tblAgileLinks we can see that the Capability Links are being stored with ObjectType = 1 not 43

      ObjectType LinkName Link
      1 DiegoCapabilityLink www.diegocapa.com
      1 DiegoEpicLink DiegoEpicLink.com
      2 DiegoFeatureLink DiegoFeatureLink.com
      3 DiegoStoryLink DiegoStoryLink.com
      44 DiegoObjectiveLink DiegoObjectiveLink.com
      5 DiegoRiskLink DiegoRiskLink,com
      64 DiegoDependencyLink DiegoDependencyLink.com

      This means that links for Capabilities are being stored in the Jira Align database as links for Epics.
      The impact is that Enterprise Insights would pull these links and they would be identified as Epic links not Capability Links.

       

      Steps to Reproduce

      1. Create a link in a Capability
      2. Run the following SQL SELECT query on the Jira Align database
        SELECT [UniqueID]
              ,[ObjectType]        
              ,[LinkName]
              ,[Link]
          FROM [LAB-ALIGN].[dbo].[tblAgileLinks]
        

        Expected Results

        UniqueID ObjectType LinkName   Link
        1 43 Capability Link   www.capabilitylink.com
        2 1 Epic Link 1   www.epiclink.com
        3 2 Feature Link   www.featurelink.com
        4 3 Story Link   www.storylink.com

      Actual Results


       

      Impact on Enterprise Insights:

      SELECT
      	   [External Reference ID]
      	, [External Reference Name]
      	, [External Reference Value]
      	, [Object Type]
      	from [export_dw].[External Reference]
      

      The Capability Link displays as an Epic Link.
       

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              dfuller@atlassian.com Don Fuller
              81fb6d9e7236 Heidi Hendry (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync