Make substatus data available

[aboks]

Makes the substatus field available. This allows distinguishing between new, ongoing and regressed issues.

[CLAassistant]

All committers have signed the CLA.

[bossinc]

Looks good! Thank you for the PR

[adamyeats]

@aboks Thanks for the contribution! There's a minor CI failure here:

26/66 ./pkg/sentry/issues.go 17.59ms X
/drone/src/pkg/sentry/issues.go:17:2 - Unknown word (Substatus)
/drone/src/pkg/sentry/issues.go:17:31 - Unknown word (substatus)

Could you add the words Substatus and substatus to the cspell.config.json and push? I would do this for you, but as this was submitted from a fork, I don't have commit rights on this PR.

[aboks]

Sure, it should be in the word list now.

[adamyeats]

@aboks Thank you! There also seems to be a failing test:

        	Error Trace:	/drone/src/pkg/handlers/handlers_test.go:29
        	Error:      	Not equal: 
        	            	expected: 32
        	            	actual  : 33
        	Test:       	TestSentryDatasource_Issues/valid_org_slug_should_not_throw_error
--- FAIL: TestSentryDatasource_Issues (0.00s)
    --- FAIL: TestSentryDatasource_Issues/valid_org_slug_should_not_throw_error (0.00s)

[aboks]

@adamyeats I don't really see how my change could cause that test to fail, or where that test failure is visible in the workflow output. I've rebased my branch on main, maybe that helps? Otherwise I'd happily give you commit permissions to my fork if that helps to resolve things.

[adamyeats]

@aboks The failing assertion tests the number of fields in a response given a valid organisation slug. You're adding an extra field to the response, so this will make the test fail. Simply incrementing the number by 1 in the assertion should fix the test.