-
Suggestion
-
Resolution: Unresolved
-
None
Currently ATLAS projects linked with Jira epics are summarised on the Issue View's details section in the form of Issue Overview on the bottom right part of the Issue View Screen. Apart from this, there are the "Project Overview Key" and "Project Overview Status" fields that link the ATLAS project key and status value.
For better visibility of ATLAS project status in Jira Epics, suggestion is to either allow for repositioning of the "Project Overview" segment on the issue layout or else to have a third custom field on Jira to track the latest project updates since such a custom field can be repositioned accordingly
[ATLAS-93] Allow repositioning of "Project Overview" segment or provision a separate JIRA custom Field to pick project updates
| Assignee | Original: Gareth Sime [ gsime ] | New: Nir Nikolaevsky [ 50c262b1a568 ] |
| Summary | Original: Allow repositioning of "Project Overview" or separate JIRA custom Field to pick project updates | New: Allow repositioning of "Project Overview" segment or provision a separate JIRA custom Field to pick project updates |
| Summary | Original: Allow repositioning of | New: Allow repositioning of "Project Overview" or separate JIRA custom Field to pick project updates |
| Summary | Original: JQL Search with Team Field Fails to Include Sub-tasks in Team-Managed Projects | New: Allow repositioning of |
| Security | Original: Atlassian Staff [ 10750 ] |
| Description |
Original:
h3. Issue Summary
Subtask inherits Team from the Parent issue key. Although, the Team data is not directly saved for the Sub-task in Jira, JQL search "Team = <>" will return both Parent and Sub-task. This JQL search is not working for TMP. h3. Steps to Reproduce # Create a Parent issue (Say, Story) with Team = "Team Guava" both in a CMP and TMP # Create Sub-task for each CMP and TMP # Run the below JQL search {code:java} Team = "Team Guava" {code} # JQL output will be missing Sub-task from TMP h3. Expected Results JQL search should return both Parent and Sub-task h3. Actual Results JQL is missing Sub-task in the search result h3. Workaround User [GET Issue Jira API|https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-get] to confirm the Team association for Subtask. API will show Team = Parent's Team in output. |
New:
Currently ATLAS projects linked with Jira epics are summarised on the Issue View's details section in the form of _Issue Overview_ on the bottom right part of the Issue View Screen. Apart from this, there are the "Project Overview Key" and "Project Overview Status" fields that link the ATLAS project key and status value.
For better visibility of ATLAS project status in Jira Epics, suggestion is to either allow for repositioning of the "Project Overview" segment on the issue layout or else to have a third custom field on Jira to track the latest project updates since such a custom field can be repositioned accordingly |
| Component/s | Original: Site - Administration [ 72713 ] | |
| Component/s | New: Search [ 69200 ] |
| Description |
Original:
h3. Issue Summary
Admin would like the ability to move Atlas project data (including projects, history, timeline, and updates) from one cloud site, or from one Atlassian Organization, to another. The recommendation today is to add a new Atlas instance to the new site and re-create details in that new instance using the original as a reference, but this doesn't bring history and updates over to the new instance. This can create friction for teams who want to bring historic Atlas data from one site to another. h3. Workarounds: Currently, there is no known workaround to move Atlas data (including projects, history, timeline, and updates) from one Atlas instance to another, even across different Atlassian Organizations. |
New:
h3. Issue Summary
Subtask inherits Team from the Parent issue key. Although, the Team data is not directly saved for the Sub-task in Jira, JQL search "Team = <>" will return both Parent and Sub-task. This JQL search is not working for TMP. h3. Steps to Reproduce # Create a Parent issue (Say, Story) with Team = "Team Guava" both in a CMP and TMP # Create Sub-task for each CMP and TMP # Run the below JQL search {code:java} Team = "Team Guava" {code} # JQL output will be missing Sub-task from TMP h3. Expected Results JQL search should return both Parent and Sub-task h3. Actual Results JQL is missing Sub-task in the search result h3. Workaround User [GET Issue Jira API|https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-get] to confirm the Team association for Subtask. API will show Team = Parent's Team in output. |
| Reporter | Original: Blair at Atlassian [ bjohnson2@atlassian.com ] | New: Nivedita Venkateswaran [ 76629e7f3532 ] |