Suddenly unable to create one specific issue type from Slack integration

[Kyle V]

Hi there. My team and I make use of the existing Slack integration. We recently lost the ability to log issues from Slack but just for one specific issue type (Task) in one project. All other issue types / projects are working fine. Unfortunately the problematic one is our most common issue type.

When we try to create one of these Tasks, we're able to see the pop-up in Slack with the required & optional fields for that issue type. Once we've filled those in, we select 'Submit', and after a few seconds we get a generic "Something went wrong! Please try again later" message.

We just noticed this behaviour today (Feb 24). The last time we were able to successfully log a Task was on Feb 21. We've have not made any changes to this Task issue type recently. We did add a new custom issue type to the project on Feb 20, but again this Task logging was working fine on the 21st.

I've tried logging out of & logging into Jira through Slack, also revoking & resetting the integration itself (just for my account, not team-wide), but no luck. Any idea what could be causing this or how to troubleshoot further?

[Trudy Claspill · Accepted solution]

Hello @Kyle Vey 

Welcome to the Atlassian community.

Have you double checked that in Slack all the fields that are Required for that issue type, both through Field Configuration and the Create transition Validators, are present when you create the issue via Slack?

Are you able to create that issue type in that project directly in the Jira UI?

[Kyle V]

Hi Trudy. 

Thanks for the warm welcome & the quick reply!

Yes, I've double checked that all of the Required fields are present in Slack when trying to create an issue. I don't have any validators on the Create transition currently. Task & Epic both share the same workflow, but the issue only seems to be present for Tasks.

And I am able to create the issue directly in Jira. No problem there.

Kyle

[Kyle V]

Update: I had configured the native 'Priority' field to be Required for this task type. Out of curiosity, I made it optional and tried again, and this time I was able to successfully log a Task from Slack. I'm not sure why that would have caused a problem suddenly, as we've had that field configured as Required for many months. 

But now I'm noticing that we're no longer seeing the automatic Slack message from Jira Cloud when we've created a new issue from Slack (across projects & issue types). The most recent one I can see is from Feb 21, so it may be fair to assume that both of these problems are related.

[Kyle V]

Another update: The secondary issue now seems to be resolved. The Jira Cloud app is automatically posting issue details in Slack when an issue is created from a Slack message again. Not sure what changed.