Search for articles created by the Mercury team to answer your questions.

Mercury Build

How can we help you?

Help Center

Enhancement

Fixed

mercury

In Review

Backlog

Planned

Next-Up

In Progress

Done

Canceled

Owner/Client Impact

Trade Partner Impact

<p>The stage of each feature request created by users.</p>

Next up

Feedback Roadmap

Hey {name|there}! 👋

<h2 id="originalattribution">* Original + Attribution:</h2>
<p>Amy Lungren  AmyLindgren@cushingterrell.com - I also think that the comments box on the submittal return causes some confusion because when a new team member is returning submittals, they may hit the ‘Respond’ button at the very bottom of the page, adding a blank comment box. Either it should give you an error for not putting anything in the comment box or possibly remove the box.</p>
<p>See Product Spec document for more.</p>
<h2 id="whatproblemarewesolving"><strong>What problem are we solving?</strong></h2>
<p>Clearer documentation for official responses held in the assignees input.</p>
<h2 id="whoarewesolvingitfor"><strong>Who are we solving it for?</strong></h2>
<p>All Users in RFI, and Submittal Tools.</p>
<h2 id="whatshouldhappen"><strong>What should happen?</strong></h2>
<p>How about we provide a cation message that says “Would you like to continue with a blank response?” after the Respond button is pressed and text area is null. Then if yes is the answer we put in the text box in light gray italic “No text provided”, so people reviewing in the future it was intentional.</p>
<h2 id="howwillweknowitsdone"><strong>How will we know it’s done?</strong></h2>
<p>Magic.</p>
<h2 id="articlestopublish">Article(s) to Publish</h2>
<p>NA</p>
<h2 id="notesconstraints"><strong>notes / constraints:</strong></h2>

Blank Response Text & Toast

Linear