How to submit bug report?

[DuncanC]

Can someone please point me to where I can find a list of reported and unresolved bugs in Survey123 and report a bug if it's not already listed?

I've found several but this one is particularly annoying and workflow breaking.  I can't believe the OP has had to have their users resort to such a terrible work around for over a year for something that's basic core functionality and just doesn't work properly.

https://community.esri.com/t5/arcgis-survey123-questions/some-select-one-questions-not-updating-when...

[RyanUthoff]

These two posts might be of use to you. Unfortunately, unless it's a critical bug, it often takes years for Esri to fix it, if at all.

https://community.esri.com/t5/arcgis-pro-ideas/display-all-known-bugs-and-their-status-online-for/id...

https://community.esri.com/t5/arcgis-pro-questions/why-aren-t-more-bug-reports-shared-publicly/td-p/...

[ChristopherCounsell]

Thanks for sharing the posts, there's some great discussion there.

I'd encourage members of the community to use the channels - more depth in my other response - when it comes to defects. Sure, some can often take a lot of time, but it's often tied to other factors like a roadmap, technical limitations and compatibility. e.g. lots of bugs fixes enhancements came with the release of the new map viewer. They strongly consider users impacted, so the more we can engage with Esri, the better they'll understand what to prioritize.

The Survey123 team is also extremely good at communication when it comes to defects. The issue, plans, timeframes, and a generally fast turnaround.

[ChristopherCounsell]

Hi @DuncanC, 

You've touched on a few points of discussion here. I have a lot of experience with Survey123 on both sides of the fence which may help you.

Can someone please point me to where I can find a list of reported and unresolved bugs in Survey123

There are several places you can find these:

1. Documentation - for known, established issues. Often tied to technical limitations or things that require time to fix:
   • https://doc.arcgis.com/en/survey123/browser/get-answers/knownissuesgetanswers.htm
2. Technical support search page - for reviewed defects that get marked as publicly visible
   • https://support.esri.com/en-us/search?s=Relevance
3. ArcGIS Online status page - for service disruptions impacting a majority of users
   • https://status.arcgis.com/
4. The community forums. The Survey123 team is amazing at communicating on issues. e.g.
   • blog; check Tricks of the Trade comments and notes https://community.esri.com/t5/arcgis-survey123-blog/bg-p/arcgis-survey123-blog
   • Recent posts - updates = users posting feedback = good discussion. See my recent posts here and here for my experience.
5. Technical support case.
   • They will search their system for submitted defects and let you know if any match your behavior/issue. 
   • Having had access to that system, I don't believe there's much value in lists of all submitted defects. A lot are junk (user error), duplicates, and potentially misleading because of the title/description. The ones publicly listed or in the documentation are the ones Esri has reviewed and tidied up to be friendly for end users. Some product teams like Survey123 openly discuss their issues on the forums ahead of the technical support system, see my earlier links.

 and report a bug if it's not already listed?

TECHNICAL SUPPORT. The answer is always technical support, even for known bugs you may come across on the community forums. Why?

• Esri tracks impact by the number (and size) of accounts attached to the defect. If we all see a bug but don't put in a support case, the measured impact is low.
• You can escalate the defect
• You can track the defect
• You can be told when your issue is not a defect, or if a workaround becomes available.

 but this one is particularly annoying and workflow breaking.  I can't believe the OP has had to have their users resort to such a terrible work around for over a year for something that's basic core functionality and just doesn't work properly.

https://community.esri.com/t5/arcgis-survey123-questions/some-select-one-questions-not-updating-when...

There is no indication to me that this is a defect. At a glance, it works fine in the field app, but not the website. The website leverages the web form. There is a lot of functionality in the field app that is not supported in the web form; I'd assume that this difference in behavior is what the poster is seeing. If it is a bug we'd need a lot more information. The community can help explore the issue but technical support has active resources to look at it. What this poster needs to do is:

• Provide the XSLForm, or the parts relevant to reproduce the issue
• Provide the workflow, desired behavior, and issue
• Provide the version of Survey123 Connect + the version of the published survey
• Work with technical support to confirm that the configuration and workflow is correct, and that there is an underlying issue with the product.

Having been on both sides, a lot of the time a 'defect' is just invalid XLSForm design or a questionable workflow. In those moments, the community or technical support can help you out. When it's a legitimate defect, technical support will have or create the case, identify potential workarounds, and you can proceed as best as possible.

I've found several

Create a community question and technical support case for each, until you have a satisfactory conclusion, which unfortunately from time to time is a bug number. Feel free to tag me in any and I'll try help where I can.