Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with status
Search options not deleted
user 16400
Questions about how a system informs the user its state or status. How and what a system tells a user about the state of the system can have a meaningful impact on the system's usability.
0
votes
1
answer
84
views
Using "Void" as a status instead of "Void" as an action
I'm having trouble deciding what the status of a document should be once a user clicks the Void button. … The current status options for a document are the following:
Draft
Pending Approval
Awaiting Response
Ready to Purchase
Void
Complete
Is there a better Status than "Void" I can use? …
- 103