Postclic premium unlimited: promotional offer at RM 4.19 for 48h, then RM 228.34 per month without commitment

Cancellation service #1 in Malaysia
Jira is a cloud-based project management and issue tracking service from Atlassian. Atlassian is an Australian software company, and Jira is widely used by development teams, IT teams, and business teams for task tracking, bug tracking, sprint planning, and workflow management.
For Malaysia users, the main thing to know is that Jira runs as a subscription service. There is a Free plan for up to 10 users, then paid plans such as Standard at $7.91 (RM37)* per user per month and Premium at $15.83 (RM75)* per user per month based on monthly billing "pricing" (atlassian.com).
Many users do not pay just for basic task lists. Paid Jira plans add features such as Rovo Search, Chat, Agents, AI-powered work features, advanced team controls, unlimited storage on Premium, and premium support. That is why some teams move up from Free quite quickly once projects become bigger.
Atlassian also says that if you are on the Free plan and exceed the user limit, you are automatically upgraded to a 7-day free trial of the Standard plan "free trial terms" (atlassian.com). If nobody in the team notices that change, billing can start after the trial ends, which is one reason cancellation questions come up so often.
Jira is available in Malaysia through the web, and some subscriptions may also be managed through App Store or Google Play if they were started there. Prices shown publicly are in USD, so for this guide they are also shown in MYR using the research conversion rate of 1 USD to about RM4.72.
Jira does not publish a public cancellation phone number. Support channels available from Atlassian include a contact page, live chat through the support page, and email at [email protected] with 24/7 support availability "support details" (atlassian.com). For local users, that means cancellation is mainly self-service online, senang if you know where to click, frustrating if you do not.
Many Jira users feel annoyed when the cancel option is hard to spot, and the bigger worry is getting billed again after thinking the job is done. Before cancelling, log in and confirm which plan is active, which site is billed, and the next billing date. Take screenshots of your current plan, billing page, and seat count.
This matters because Atlassian states that Cloud subscriptions end at the end of the current billing cycle, not on the same day you click cancel "cloud licensing" (atlassian.com). For monthly subscriptions, Atlassian also uses Maximum Quantity Billing, meaning the bill is based on the highest number of seats assigned at any point in the billing cycle, so reducing users near month end may not reduce the current bill.
If you subscribed directly with Atlassian, the main route is through your Atlassian account. The verified click path is to log in to Atlassian Cloud billing guidance, go to my.atlassian.com, select Atlassian Cloud from the list of apps or subscriptions, then click Cancel Subscription or Cancel Trial to request cancellation "cloud licensing" (atlassian.com).
After that, the subscription stays active until the end of the current billing cycle, and Atlassian says your credit card will not be charged again after the cancellation takes effect "cloud licensing" (atlassian.com). If the button is missing, check whether you are in the right site, whether you are a billing admin, and whether the subscription was actually started through Apple or Google instead of direct web billing.
If the Jira subscription was bought on iPhone or iPad, open App Store, tap your profile icon in the top right, choose Subscriptions, open the Jira subscription, then tap Cancel Subscription. This only works for subscriptions billed by Apple, not for direct Atlassian web billing.
If the subscription was bought on Android, open Google Play Store, tap the menu icon, choose Subscriptions, open Jira, then tap Cancel Subscription. A common mistake is trying to cancel inside Jira when the billing is handled by Apple or Google. In that case the cancel option inside Atlassian may not appear at all.
If self-service fails, use Atlassian support through the official cancel or unsubscribe contact page. Atlassian lists live chat there, email [email protected], and 24/7 support hours. No public phone number is available, so do not waste time hunting for one.
When you contact support, include your site name, invoice number, last 4 digits of the card if relevant, cancellation date requested, and screenshots showing the active plan. If you want extra proof, you can also send a registered letter to Atlassian if you have a valid business address from your own records. Some Malaysia users now use certified digital post services such as Postclic for time-stamped proof of sending and receipt instead of traditional registered mail.
No specific dark pattern was identified in the verified research, but user feedback shows the interface itself can be the problem. Jira is often criticised for a steep learning curve, and some users report slow loading that makes billing pages harder to navigate when you are already trying to leave.
If you cannot remove a card because the system says there is still an active subscription, do not start with the card screen. Go back to the subscription list, confirm whether the plan still shows Standard or Premium, and cancel the product first. Card removal usually comes after the subscription status changes.
The key timing rule is simple. If you cancel a Jira Cloud subscription, Atlassian says the service is terminated at the end of the current billing cycle, and your card should not be charged again after that point "cloud licensing" (atlassian.com).
That means if your billing date is on the 25th and you cancel on the 10th, access normally continues until the 25th. You are not cutting access immediately in the usual web cancellation flow, which helps teams finish urgent exports or handovers before the site closes.
Atlassian does not clearly publish an auto-renewal clause in the specific terms data provided here, but the practical result of an active paid subscription is recurring billing until cancellation is completed. Trial users should be extra careful because Atlassian says exceeding the Free plan user limit can trigger a 7-day Standard trial "pricing" (atlassian.com).
If that trial converts and nobody cancels it in time, the team may move into paid billing. Put a calendar reminder a few days before the next invoice date so there is no last-minute panic.
This is the part many people regret missing. Atlassian states that if you unsubscribe from all Jira products on your site, your Jira data will be deleted immediately "data deletion after unsubscribe" (atlassian.com).
So do not assume you can come back next week and still export projects. Before cancelling the last Jira product on a site, export issues, attachments, workflows, reports, and any admin settings you may need for audits or migration.
Refunds for cloud subscriptions are available only within the first paid month after the trial period for monthly subscriptions, and within 30 days of payment for annual subscriptions "refund policy" (atlassian.com). Outside those windows, Atlassian says refunds cannot be offered.
There is also no credit for cancelling before the end of a billing cycle "cloud licensing" (atlassian.com). In plain terms, most users should not expect a pro-rated refund for unused days left in the month. That is one of the biggest surprises for teams that cancel early and assume they will get part of the money back.
If you are still within the eligible window, use Atlassian's refund support page and the support contact page. Prepare your invoice number, payment date, amount, site URL, and the reason for the request, such as accidental renewal or duplicate subscription.
For a stronger case, attach screenshots showing the cancellation date and the account status. If the charge came through App Store or Google Play, request the refund through Apple or Google first because those stores control their own billing channel.
In Malaysia, the Consumer Protection Act 1999 does not give a universal cooling-off right for all digital subscriptions. A 10 working day cooling-off period exists for direct sales contracts under the Direct Sales and Anti-Pyramid Scheme Act 1993, but that usually does not fit a normal online Jira subscription bought directly on the web.
So for Jira, your refund rights usually depend more on Atlassian's own refund policy and on whether the charge was unauthorised, duplicated, or misleading. If the company ignores a valid billing complaint, you can raise it with KPDN or consider TTPM for consumer claims, depending on the facts and claim amount.
If you cancelled properly and still got charged, or if the charge looks unauthorised, ask your issuing bank for a chargeback or to dispute a recurring card transaction. In Malaysia, banks usually work within card-network timelines of around 60 to 120 days from the transaction date or from when you discovered the problem.
Have your evidence ready: cancellation screenshot, support emails, invoice, and bank statement entry. This sits within Bank Negara Malaysia's financial consumer protection framework under the Financial Services Act 2013 or Islamic Financial Services Act 2013, so banks are expected to handle complaints properly.
No minimum commitment duration was found in the terms data reviewed for this guide "terms data" (atlassian.com). That is good news for users who want flexibility, because no early termination fee was found either.
The more practical risk is trial conversion. Atlassian says that if a Free plan exceeds the user limit, it automatically upgrades to a 7-day free trial of Standard "pricing" (atlassian.com). If no one notices that upgrade, paid billing may begin after the trial window ends.
The clearest term for cancellation impact is data loss. Atlassian states that if all Jira products on the site are unsubscribed, Jira data is deleted immediately "data deletion after unsubscribe" (atlassian.com). That line should shape your cancellation plan more than anything else.
The research did not find specific published details here on applicable law, dispute resolution, or a detailed auto-renewal clause in the archived product terms reviewed. That lack of clarity does not stop you from cancelling, but it does mean you should preserve your own records carefully if a billing dispute starts later.
| Plan | Price (USD / MYR) | Billing period | Main features |
|---|---|---|---|
| Free | $0.00 (RM0)* | Monthly | Up to 10 users |
| Standard | $7.91 (RM37)* | Monthly | AI work features |
| Premium | $15.83 (RM75)* | Monthly | Unlimited storage, premium support |
Prices are approximate, converted from USD at 1 USD ≈ 4.72 MYR. Check the official Jira pricing page for exact local prices and taxes.
The cheapest option is Free at RM0 for up to 10 users. The most expensive monthly option in the verified data is Premium at $15.83 (RM75)* per user per month, which is about double Standard at $7.91 (RM37)*.
For small Malaysia teams, Standard is often the point where costs start creeping up because every added seat matters and Maximum Quantity Billing can lock in a higher monthly charge if headcount spikes during the cycle. Premium makes more sense only if you really need unlimited storage and 24/7 premium support.
Atlassian states that annual billing options are available with potential savings up to 17% compared with monthly billing "pricing notes" (atlassian.com). If your team is downsizing soon, shifting into an annual cycle at the wrong time can leave you paying for more than you need.
No cancellation fee was found in the terms, and no early termination fee was found either. The real cost issue is that cancelling early does not generate a billing-cycle credit, so timing your cancellation close to renewal matters a lot.
For Malaysia users, the main consumer law is the Consumer Protection Act 1999. It does not create a universal right to cancel every online subscription just because you changed your mind, so Jira users usually rely on the contract terms, billing evidence, and protections against unfair or misleading conduct.
The 10 working day cooling-off rule under the Direct Sales and Anti-Pyramid Scheme Act 1993 applies to direct sales contracts, not automatically to a standard online SaaS purchase like Jira. So if your issue is an unwanted renewal or charge after cancellation, your strongest path is usually proof of what happened, not a general cooling-off claim.
If Atlassian support does not solve a billing problem, file a complaint with KPDN and gather every document before you submit. Include invoices, screenshots, your cancellation request, email replies, bank statement entries, and the date the charge happened.
If the dispute involves money you want returned, TTPM can be relevant for a consumer claim. State the timeline clearly, such as the cancellation date, the next billing date, and the amount charged, because vague complaints often go nowhere.
KPDN is the Ministry of Domestic Trade and Cost of Living, and it is the right authority to mention when a subscription seller ignores a clear complaint. TTPM is the Tribunal for Consumer Claims Malaysia, which can be useful if you are seeking a practical money claim after failed resolution attempts.
The research block also names MCMC, but for a Jira billing dispute KPDN and TTPM are generally the more relevant bodies for consumer complaint escalation in Malaysia. Use MCMC only if your issue overlaps with communications service matters rather than a standard software billing complaint.
Based on the review set provided, cancellation looks difficult rather than smooth. The sentiment trend is 0 positive and 4 negative out of 4 unique reviews, with recurring complaints about charges after cancellation, hidden subscription status, and trouble finding the cancel button.
That does not mean Jira is a bad product overall. Many teams still choose it for strong workflow tools and integrations. But on cancellation alone, the small evidence set here points to friction, especially when billing admin access or the original purchase channel is unclear.
| Theme | Frequency | Typical example |
|---|---|---|
| Charge after cancel | 1 review | Billing continued |
| Cancel button missing | 2 reviews | Could not find option |
| Card removal blocked | 1 review | Active plan remained |
| Source | Rating | Number of reviews |
|---|---|---|
| TrustPilot | 1/5 | 1 |
| Atlassian Community | Unrated | 3 |
Local usability complaints also fit this pattern. Users report Jira's interface is complex and has a steep learning curve, while some report slow load times. When a billing page is already confusing, those issues can make cancellation feel worse than it should, lah.
Prepare your evidence before touching the subscription. Save a screenshot of the current plan name, billing page, seat count, and next invoice date. If your team may switch tools, export your Jira data before unsubscribing from the last Jira product because Atlassian says data can be deleted immediately after full unsubscribe "data deletion" (atlassian.com).
Also save the site URL, workspace name, and the name of the billing admin account used to manage the subscription. Many cancellation delays happen because the person trying to cancel is logged into the wrong Atlassian identity.
If you plan to ask for a refund, keep the invoice number, payment date, amount charged, card statement line, and any trial end date. If the charge was $7.91 (RM37)* or $15.83 (RM75)* per user, note the exact number of seats on the invoice because seat count disputes can matter under Maximum Quantity Billing.
After cancelling, save the confirmation email and take a screenshot of any on-screen message showing cancellation status. Then watch your bank or card statement through the next billing date and at least one cycle after that.
A classic mistake is trying to cancel in Atlassian when the subscription was started through App Store or Google Play. If Apple or Google handles billing, the web account may not show the correct cancellation control, and users can waste days clicking around the wrong dashboard.
The fix is simple. Match the cancellation method to the original billing channel. Check your invoice sender or app store purchase history before doing anything else.
Some users think lowering seat count to zero or deleting the billing card will automatically end the paid plan. Review evidence shows that card removal can be blocked while an active subscription still exists, and the plan may continue showing Standard even after a failed downgrade attempt.
Always cancel the subscription itself first. Only after the product status updates should you try to remove the card or close the site.
Another common misunderstanding is thinking that cancelling halfway through the month will trigger a partial refund. Atlassian says no credit is offered for cancelling before the end of a billing cycle "cloud licensing" (atlassian.com).
If you want to limit cost, cancel before the next billing date rather than after a fresh renewal. That timing matters more than people expect.
Jira's Free plan can auto-upgrade to a 7-day Standard trial if you exceed the user limit "pricing" (atlassian.com). Teams often add members quickly during a project rush and only notice later that the site is no longer on Free.
Take a screenshot of the plan after adding new users. If it shows a trial, put a reminder in your calendar straight away so the team can decide whether to stay or cancel.
One negative review in the dataset mentions continued charges after an earlier cancellation claim. Whether the fault was system, account access, or confusion, the lesson is the same: a click without proof is weak evidence in a billing dispute.
Save the confirmation page, email, support ticket number, and statement record. If billing continues, that bundle makes support, chargeback, KPDN complaint, or TTPM claim much easier.
| Method | Notice period | Fee | Difficulty |
|---|---|---|---|
| Web/account | Before next billing date | No fee found | Easy |
| App Store (iOS) | Before next billing date | No fee found | Medium |
| Google Play (Android) | Before next billing date | No fee found | Medium |
| Registered mail | 5-10 business days | No fee found | Higher, strong proof |
Web cancellation is the fastest when the subscription was bought directly from Atlassian and you have billing admin access. App Store and Google Play are slightly more awkward because they depend on the store account owner, but they still work fine once you confirm the purchase channel.
Registered mail is slower, yet it can help if you need a strong paper trail. It is not the main route for Jira, because the service is designed around online account management rather than postal processing.
As soon as you cancel, look for a confirmation screen or email and save it. Then put a reminder one or two days before the next billing date and another reminder a week after that date to verify that no new charge appears.
If the site remains active until cycle end, use that remaining time to export anything still needed. Do not leave exports until the last hour because slow loading has been reported by some users.
Monitor your card or bank statement for at least one full billing cycle after cancellation. If a recurring charge appears after the effective end date, contact Atlassian support immediately and ask your bank about a chargeback or recurring transaction dispute if support does not fix it.
In Malaysia, chargeback timing is commonly around 60 to 120 days depending on the bank and card network. The sooner you act, the better your chances, especially if you already saved the cancellation proof.
If you are cancelling because Jira feels too complex, Linear is a simpler issue tracker priced from $8 (RM38)* per user per month. ClickUp starts from $7 (RM33)* per user per month and combines tasks, documents, goals, and chat, while Notion starts from $10 (RM47)* per user per month and works well for flexible project documentation.
Those prices are also based on USD source figures, so local tax and final billing can differ. Still, they give a practical benchmark if your team is comparing value after a Jira exit.
No physical cancellation address was found in the verified research for this guide. Jira cancellation is therefore best treated as an online-first process through your Atlassian account, App Store, Google Play, or the official Atlassian support page.
This matters because some users waste time looking for a postal address when the actual cancellation control is tied to the billing channel and admin access. For most Malaysia users, the fastest route is still digital account management.
If your case involves a billing dispute, build your written trail through support tickets, email to [email protected], screenshots, invoices, and statement records. That evidence is usually more useful than sending an untracked letter to a general corporate office.
If you still choose post for your own records, send only after identifying the correct business address from your account documents or invoice records. Pair it with your online support complaint so there is a clear timeline showing when you asked for cancellation.
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.