{"id":5454,"date":"2026-09-23T09:20:49","date_gmt":"2026-09-23T13:20:49","guid":{"rendered":"https:\/\/carleton.ca\/cutheme-docs\/?p=5454"},"modified":"2026-09-24T09:18:00","modified_gmt":"2026-09-24T13:18:00","slug":"why-we-ask-you-to-use-jira-for-support-requests","status":"publish","type":"post","link":"https:\/\/carleton.ca\/cutheme-docs\/2026\/why-we-ask-you-to-use-jira-for-support-requests\/","title":{"rendered":"Why We Ask You to Use Jira for Support Requests"},"content":{"rendered":"\n
\n
\n\n
\n
\n
\n

\n Why We Ask You to Use Jira for Support Requests\n <\/h1>\n \n \n \n\n

Our team is committed to providing timely, effective, and transparent support. Whether you’re reporting an issue, requesting a change, or seeking technical assistance, the way a request enters our queue has a direct impact on how quickly and efficiently we can respond.<\/p>\n\n\n\n

\n
Request IT Help<\/a><\/div>\n\n\n\n
Website Support<\/a><\/div>\n<\/div>\n\n\n <\/header>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n<\/section>\n\n\n\n

For that reason, we ask that all support requests be submitted through Jira and that all communication related to those requests remain within the Jira ticket whenever possible.<\/p>\n\n\n\n

Why Not Email or Teams Messages?<\/h2>\n\n\n\n

It may seem faster to send an email or Teams message directly to someone you know on our team, but in practice, this often has the opposite effect.<\/p>\n\n\n\n

Individual mailboxes and chat conversations are not designed to manage support requests. Messages can be missed, buried among other work, delayed while someone is away, or become disconnected from the broader context of a request.<\/p>\n\n\n\n

Most importantly, direct messages create an invisible queue. While the sender and recipient may be aware of a request, the rest of the team is not. If that individual is unavailable or working on higher-priority issues, the request may sit unnoticed when it could otherwise be reviewed and assigned through our normal support process.<\/p>\n\n\n\n

What feels like a shortcut can actually result in slower resolution times.<\/p>\n\n\n\n

Why Jira Works Better<\/h2>\n\n\n\n

Jira provides a single source of truth for every support request.<\/p>\n\n\n\n

When a request is submitted through Jira:<\/p>\n\n\n\n

    \n
  • The work is tracked and prioritized appropriately.<\/li>\n\n\n\n
  • All team members can see the request and assist when needed.<\/li>\n\n\n\n
  • Decisions, updates, and technical details are captured in one place.<\/li>\n\n\n\n
  • Requesters have visibility into the status of their issue.<\/li>\n\n\n\n
  • Historical information is available for future reference.<\/li>\n\n\n\n
  • Work can continue even if a team member is unavailable.<\/li>\n<\/ul>\n\n\n\n

    This is particularly important because support is a team function, not an individual function. While you may have worked with a specific team member in the past, requests are often reviewed by multiple people and may be assigned based on expertise, workload, availability, and current priorities.<\/p>\n\n\n\n

    By using Jira, your request becomes visible to the entire team rather than relying on a single person’s inbox.<\/p>\n\n\n\n

    Keep the Conversation in the Ticket<\/h2>\n\n\n\n

    Once a ticket has been created, we ask that all ongoing discussion remain within Jira comments.<\/p>\n\n\n\n

    This ensures that everyone involved has access to the same information and that a complete record of the request is maintained. If questions are asked or updates are provided through email or Teams, those details may not be visible to everyone working on the issue.<\/p>\n\n\n\n

    Support requests often involve multiple conversations, technical investigations, and decisions over time. Keeping those discussions within the ticket allows anyone working on the request to quickly understand its history without having to search through emails or chat messages.<\/p>\n\n\n\n

    There are some exceptions. In situations where files, screenshots, documents, or other materials cannot be attached directly to Jira, a Service Desk agent may ask you to provide them through another method. Even in those cases, the outcome of the discussion should be documented in the ticket so that the full history remains available.<\/p>\n\n\n\n

    Fair and Consistent Support<\/h2>\n\n\n\n

    Using Jira also helps ensure that support requests are handled fairly and consistently.<\/p>\n\n\n\n

    Our team receives requests from across the university, many of which compete for the same resources. Jira allows us to review, prioritize, and assign work based on urgency, impact, complexity, and available capacity.<\/p>\n\n\n\n

    When requests are managed through email or private messages, it becomes much more difficult to track workload and ensure that all requests are receiving appropriate attention.<\/p>\n\n\n\n

    A centralized queue helps us provide consistent service to everyone rather than relying on who happened to contact a particular individual.<\/p>\n\n\n\n

    Helping Us Help You<\/h2>\n\n\n\n

    Using Jira is not about creating extra steps or bureaucracy. It is about ensuring that requests are not lost, that work can be tracked effectively, and that our team can provide the highest level of service possible.<\/p>\n\n\n\n

    When all requests and communication remain within the ticketing system, we can respond more efficiently, collaborate more effectively, and provide better support for everyone.<\/p>\n\n\n\n

    The best way to ensure your request receives the attention it deserves is simple: submit it through Jira and keep the conversation in the ticket.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Need support? Submitting requests and keeping discussions in Jira helps us respond faster, collaborate better, and avoid delays.<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":true,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[75,1],"tags":[],"class_list":["post-5454","post","type-post","status-publish","format-standard","hentry","category-featured-post","category-news"],"acf":{"cu_post_thumbnail":""},"_links":{"self":[{"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/posts\/5454","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/comments?post=5454"}],"version-history":[{"count":3,"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/posts\/5454\/revisions"}],"predecessor-version":[{"id":5488,"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/posts\/5454\/revisions\/5488"}],"wp:attachment":[{"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/media?parent=5454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/categories?post=5454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/carleton.ca\/cutheme-docs\/wp-json\/wp\/v2\/tags?post=5454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}