Summary

In Agility projects, when starting sprints using the mobile app for Jira, the 'Board' page for that board, which displays the currently active sprint, breaks when opened in desktop browsers. This happens because the GOAL is set as null in the database, which is not correctly handled by the JavaScript handling the board.

Apparently, this is only breaking Agility projects, as regular projects can handle null GOALs.

Steps to Reproduce

1. Create an Agility project
2. Enable sprints
3. Create a sprint
4. Open Jira in a mobile app and start the sprint there
5. Open board in web version (desktop browser)

Expected Results

The board opens correctly.

Actual Results

The board fails with the following error:

Something's gone wrong
Our team has been informed. If the problem persists, please contact Atlassian Support.

These errors appear in JavaScript Console in the browser:

react-dom.production.min.js:187 TypeError: Cannot read property 'trim' of undefined
    at sprint-selectors.js:31
    at index.js:76
    at index.js:36
    at index.js:90
    at index.js:36
    at Function.mapToProps (index.js:31)
    at i (wrapMapToProps.js:43)
    at Function.i.mapToProps (wrapMapToProps.js:52)
    at i (wrapMapToProps.js:43)
    at selectorFactory.js:26
qn @ react-dom.production.min.js:187
view.js:41 Uncaught TypeError: Cannot read property 'trim' of undefined
    at sprint-selectors.js:31
    at index.js:76
    at index.js:36
    at index.js:90
    at index.js:36
    at Function.mapToProps (index.js:31)
    at i (wrapMapToProps.js:43)
    at Function.i.mapToProps (wrapMapToProps.js:52)
    at i (wrapMapToProps.js:43)
    at selectorFactory.js:26

Workaround

1. Find the ID of the affect sprint (a sprint that was started in the Agility project with 'null' GOAL)
2. Edit its GOAL to an empty string (or any other string) using REST API. An example using curl:

   curl -D- -u <user>:<password> -X POST -H "Content-Type: application/json" --data '{
         "goal": ""
       }' https://instance.atlassian.net/rest/agile/1.0/sprint/<sprint ID>
   

   • Be careful: Use POST to perform a partial sprint update, DO NOT use PUT (full sprint update), which may update all other field to null causing irreversible sprint data loss