Summary

• You have a board filter that shows issues from all projects on your instance
• A new "Agility" project is created
• The statuses "To Do", "In Progress" and "Done" associated to the newly created Agility project will need to manually mapped to the existing board
• Statuses need to be manually mapped

Environment

• Jira Software

Steps to Reproduce

1. Create a new board with a filter that displays issues from all projects on the instance. Something the below JQL should work:

   status IS NOT EMPTY
   

2. Check the column mappings on the new board (Board Settings > Columns)
3. Create a new Agility project
4. Check column mappings on the newly created board

Expected Results

• Statuses are mapped as per the list of statuses in https://<host_name>.atlassian.net/secure/admin/ViewStatuses.jspa i.e. no duplicate statuses listed
• No manual mapping of statuses required as "To Do", "In Progress" and "Done" statues are already mapped
• "Duplicate" entries should be removed - see Notes

Actual Results

Before new Agility project created	After new Agility project created

Notes

• This behaviour is technically correct, as new(hidden) statuses are created for Agility projects
• This is listed as a Bug and not a Feature Request because having to map "duplicate" statuses isn't intended behaviour

Workaround

• Manually map the statuses
• Use the ticket counts(shown in the status cards) as a guide if not all statuses should be mapped