Issue Summary

• Feature (Jira Epic) has four fields w.r.t. timelines- Target Sprints: Target Start, Target Completion && Dates: Start and Target Completion.
• Dates: Start and Target Completion are derived from Date Labels defined in JA Administration > Settings > Platform Terminology > Date Labels > Start / Initiation, Target Completion --- working/expected
• Target Sprints: Target Start field is not derived from platform terminology — working/expected.
• Target Sprints: Target Completion is also being derived from the Platform Terminology > Date Label > Target Completion - Not Expected. Reason: Sprint is a logical name for a date range and not an actual date. So, it should not derive the terminology defined under platform terminology.

Steps to Reproduce

1. Note down existing Field Labels from a Feature: Target Sprints: Target Start, Target Completion && Dates: Start and Target Completion
2. Modify JA Administration > Settings > Platform Terminology > Date Labels > Start / Initiation to "Test Start"
3. Modify JA Administration > Settings > Platform Terminology > Date Labels > Target Completion to "Test Target End Date"
4. Go back to any Feature and notice how the field labels Target Sprints: Target Start, Target Completion && Dates: Start and Target Completion are derived
5. Dates: Start and Target Completion change to Test Start and Test Target End Date – expected/working
6. Target Sprints: Target Start remains unchanged (independent of platform terminology date label)
7. Target Sprints: Target Completion changes to Test Target End Date – not expected as sprint is not a date but a name of time frame.

Expected Results

Target Sprints: Target Completion field on Feature should not fetch the date label from Platform Terminology > Date Labels 

Actual Results

Target Sprints: Target Completion field on Feature fetches date label from Platform Terminology > Date Labels

Workaround

None