{"id":3049,"date":"2026-11-19T11:03:54","date_gmt":"2026-11-19T09:03:54","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3049"},"modified":"2026-11-19T11:05:09","modified_gmt":"2026-11-19T09:05:09","slug":"the-developer-needs-more-than-the-button-on-the-right","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/the-developer-needs-more-than-the-button-on-the-right\/","title":{"rendered":"The Developer Needs More Than \u201cthe Button on the Right\u201d"},"content":{"rendered":"<p>\u201cThe button on the right doesn\u2019t work\u201d leaves a developer several questions away from the problem. Which page, which button, which screen size, and what happened when you used it? A useful report lets someone attempt the same action under recognisable conditions.<\/p>\n<h2>Describe the visible failure before diagnosing it<\/h2>\n<p>Name what you tried and what you observed. \u201cAfter I submitted the enquiry form, the page stayed on the form and showed no confirmation\u201d is more useful than \u201cthe form script is broken.\u201d The first describes evidence; the second assumes a cause that may not yet be established.<\/p>\n<p>The sample below is fictional and uses a reserved example address. It illustrates a report\u2019s structure, not an observed bug or a test we performed. Replace each value with details from the actual environment and avoid including real customer data in screenshots or sample submissions.<\/p>\n<h2>Use this implementation-ready report template<\/h2>\n<blockquote>\n<p><strong>Summary:<\/strong> Enquiry form shows no confirmation after submission on narrow screen<\/p>\n<p><strong>Location:<\/strong> https:\/\/example.com\/project-enquiry\/ \u2014 project enquiry form, \u201cSend enquiry\u201d button after the message field<\/p>\n<p><strong>Environment:<\/strong> Staging; review version dated 19 November. Record the actual browser name and version, operating system and viewport dimensions used.<\/p>\n<p><strong>Starting condition:<\/strong> Visitor is signed out. Form is initially empty. Use the agreed harmless test details.<\/p>\n<p><strong>Steps:<\/strong> 1. Open the page directly. 2. Complete the required fields with the test details. 3. Activate \u201cSend enquiry\u201d once. 4. Wait for the expected response and record what appears.<\/p>\n<p><strong>Expected:<\/strong> The agreed confirmation state tells the visitor whether the enquiry was accepted and what happens next.<\/p>\n<p><strong>Observed:<\/strong> Describe the actual visible message, page change or absence of feedback. Record whether entered text remains. Do not infer whether an email was delivered from the page alone.<\/p>\n<p><strong>Repeatability:<\/strong> State how many attempts you made and the outcomes; if not retested, say so.<\/p>\n<p><strong>Evidence:<\/strong> A screenshot showing the form and any visible message, plus the time of the attempt. Redact personal information and access tokens.<\/p>\n<\/blockquote>\n<h2>Use a stable description of the element<\/h2>\n<p>\u201cOn the right\u201d can change meaning when the layout rearranges on a phone. Pair the page address with a visible label and surrounding context. If two buttons have the same label, explain which section contains the relevant one. A screenshot annotation can help locate it, but it should not replace the text someone needs to repeat the action.<\/p>\n<p>Record the conditions that could matter without turning the report into a system inventory. A signed-in preview and a signed-out public view may be different starting points. Likewise, a specific viewport helps another person attempt the same layout. If you do not know a detail, mark it unknown rather than guessing.<\/p>\n<h2>Keep expected behaviour separate from observation<\/h2>\n<p>The expected result should come from an agreed requirement or a clearly stated question. \u201cIt should work\u201d does not define the finish. If the confirmation wording has never been decided, say that the requirement is unresolved. The developer may need a product decision as well as a technical investigation.<\/p>\n<p>Mozilla\u2019s <a href=\"https:\/\/bugzilla.mozilla.org\/page.cgi?id=bug-writing.html\" target=\"_blank\" rel=\"noopener\">bug-writing guidance<\/a> emphasises precise reproduction steps and separate expected and actual results. Those principles are useful here even though a client-website report has a different audience and workflow. You do not need to copy an entire browser-project reporting process to make one website issue understandable.<\/p>\n<h2>Report one issue, then verify the same question<\/h2>\n<p>Keep an unrelated spelling correction out of the form-failure report. Link separate issues if they appear connected, without asserting a shared cause. When the developer provides a revision, return to the original route, conditions and steps. Record what now happens and whether another state remains untested.<\/p>\n<p>A completed report is not proof that the failure affects every visitor. It is an inspectable starting point for implementation and a way to recognise whether the stated problem has been addressed.<\/p>\n<p>Include the location, the conditions and the observed behaviour before proposing a fix. A visual feedback method is worth evaluating on whether it preserves those details for implementation.<\/p>\n<h2>A useful next step<\/h2>\n<p>For the next decision, read <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/a-client-comment-is-a-clue-not-yet-a-design-instruction\/\">A Client Comment Is a Clue, Not Yet a Design Instruction<\/a> and <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/resolved-is-not-the-same-as-ready-to-launch\/\">\u201cResolved\u201d Is Not the Same as \u201cReady to Launch\u201d<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Write a website issue report a developer can reproduce. Use the template to capture the page, element, conditions, steps and expected versus actual result.<\/p>\n","protected":false},"author":1,"featured_media":3085,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[35],"tags":[],"class_list":["post-3049","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-digital-tools"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/np-06-01.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3049","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3049"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3049\/revisions"}],"predecessor-version":[{"id":3181,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3049\/revisions\/3181"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3085"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}