Postclic premium unlimited: promotional offer at ₱61.60 for 48h, then ₱3,353.56 per month without commitment

Cancellation service #1 in Philippines
Jira is a cloud software service used for project management, issue tracking, and agile team workflows. It is part of Atlassian, an Australian software company founded in 2002, and Jira has long been one of the best-known tools for software teams handling sprints, bugs, and internal task boards.
If you are cancelling from the Philippines, the main thing to understand is that Jira is usually billed as a recurring SaaS subscription, not as a one-time purchase. That means your plan renews automatically unless you cancel before the next billing date, and the minimum service term listed in Atlassian's terms is one month "atlassian.com".
Most paid users are not paying just for a task list. They are paying for team collaboration features, permissions, reporting, automation, and advanced administration. Atlassian also offers a Free plan for up to 10 users, so many teams start there and then move into Standard or Premium when they need more control and storage "atlassian.com".
Jira Cloud Standard and Jira Cloud Premium can both begin with a free trial, which matters for cancellation because trial accounts can convert into paid plans if nobody stops the subscription in time. The Free plan is permanent for eligible small teams, while paid plans are the recurring ones that usually trigger refund disputes and surprise renewals.
For Philippine users, the cancellation flow is mostly online through Atlassian account portals such as my.atlassian.com or admin tools, not through a local branch office. Pricing is published by plan tier, and for this guide the available figures are Free at ₱0.00 monthly, Standard at ₱1,500.00 monthly, Premium at ₱3,000.00 monthly, and Enterprise on custom annual pricing.
Heads up, many local users get frustrated when the billing page is separate from the product itself. The truth is, Jira's setup can feel more complicated than it should be because your workspace, billing owner, app marketplace purchases, and mobile store subscriptions may all sit in different places. If you are switching after cancellation, common alternatives include Asana, Smartsheet, and GitScrum, with GitScrum starting at $8.90 (₱499) per user monthly based on a rough PHP conversion.
Many Jira users get upset for three reasons: the cancel button is not where they expect, billing keeps going after they thought they cancelled, and refunds are often denied. User complaints in 2025 show exactly that pattern, including continued charges after an account was believed to be cancelled and poor support follow-up (TrustPilot).
Before cancelling, open your billing page and note the exact renewal date. Also save a screenshot of your current plan, your workspace name, and the last successful payment amount. If your team stores important tickets, attachments, or sprint history in Jira, export what you need before cancelling because post-cancellation access is limited to 15 more days after the subscription period ends "atlassian.com".
If you subscribed directly with Atlassian, the verified path is through your account portal. Sign in at my.atlassian.com, select Atlassian Cloud from your app or subscription list, then click Cancel Subscription or Cancel Trial. Atlassian states that the cloud subscription ends at the close of the current billing cycle, and your card should not be charged again after that point "support.atlassian.com".
The practical detail that catches people off guard is this: cancelling does not usually stop access the same day. You keep access until the end of the active billing cycle, and Atlassian also says there is no credit for cancelling before that cycle ends. If you want product help pages while doing this, Atlassian's support center is here: Jira help page.
If the Jira charge is coming through Apple or Google instead of Atlassian directly, cancel in the same store where you started the subscription. On iPhone or iPad, open App Store, tap your profile icon, choose Subscriptions, open the Jira subscription, tap Cancel Subscription, then confirm "support.apple.com".
On Android, open Google Play Store, tap the menu or profile area, choose Subscriptions, select the Jira subscription, tap Cancel Subscription, and follow the prompts "support.google.com". A very common mistake is cancelling inside Jira while the actual recurring charge is controlled by Apple or Google. If your receipt comes from Apple or Google, cancel there or the billing may continue.
Atlassian's verified public support details in the provided sources do not list a customer service phone number, live chat, or direct billing email for cancellation. So the realistic route is online account cancellation first, then formal evidence gathering if something goes wrong. That means screenshots, invoices, and the exact date and time you clicked cancel.
If you need a paper trail, you can also send a registered letter to the Manila office for general contact purposes, although the actual subscription process is online. Some consumers now use digital registered mail services such as Postclic because they provide timestamped proof of sending, receipt, and opening with tracking. Use postal mail as a backup record, not as your main cancellation channel.
When you cancel a direct Jira Cloud subscription, Atlassian says the service is terminated at the end of the current billing cycle, not immediately "support.atlassian.com". So if your renewal date is on the 28th and you cancel on the 10th, you should generally keep paid access until the 28th.
This is where many users get confused. They see the cancellation request succeed and assume billing should be reversed for the rest of the month. Jira does not promise that. The subscription simply runs to the end of the paid term, and no prorated credit is offered for the unused remainder of that cycle.
Atlassian's terms say your subscription automatically renews for another term equal to the original subscription term unless cancelled before the current term expires "atlassian.com". For monthly plans, that usually means another month. For annual plans, that can mean a much larger renewal amount in one charge.
If you are on a trial, this matters even more. Jira Cloud Standard and Premium can begin as free trials, and if nobody on the billing side stops the plan before the trial ends, the account can move into paid service. That is why a calendar reminder 3 to 5 days before the trial end date is a simple but very effective safeguard.
Atlassian says that after your subscription period ends, you can still access your site for 15 more days. After that, the site is deactivated, and product data is retained for a period that depends on the plan "atlassian.com".
Take note, that 15-day window is not a reason to delay exports. If your team needs project histories, attachments, audit records, or customer-facing tickets, export before the billing period ends. Once the site is deactivated, recovery becomes much harder and may require support involvement that is not clearly documented in the public cancellation page.
Jira's public refund policy for cloud subscriptions is narrow. Monthly subscriptions are eligible only within the first paid month after the trial period, and annual subscriptions are eligible within 30 days of payment "support.atlassian.com". After those windows, Atlassian says refunds cannot be offered.
That means many people asking for money back after a normal renewal will not get a prorated refund. This lines up with user complaints saying support relied on policy instead of making exceptions, even where there was little or no usage after renewal (TrustPilot).
Start with the same billing environment where the charge occurred. For a direct Atlassian charge, sign in to the relevant Atlassian billing account, collect the invoice number, payment date, plan name, and cancellation screenshot, then use Atlassian's refund guidance here: Refund help page.
If the charge came from App Store or Google Play, request the refund through Apple or Google because they control the payment record. This is often the fastest route for store-based subscriptions. For all channels, include the exact amount, such as ₱1,500.00 or ₱3,000.00, and the date of the charge to reduce back-and-forth.
In the Philippines, subscription complaints can fall under the Consumer Act of the Philippines, Republic Act No. 7394, with DTI as the main consumer authority for this type of dispute. There is no universal statutory cooling-off period for all online subscriptions, so Jira's own refund window usually matters more than a general online cancellation right.
If you are dealing with an unauthorized or continued charge after cancellation, you can also ask your bank, credit card issuer, GCash, or Maya for a dispute or chargeback. Under BSP-related card dispute practice, cardholders commonly have up to 60 days from the statement date to contest a transaction. Save your cancellation confirmation and screenshots because that evidence can decide the case.
Atlassian's terms say the minimum term of service is one month, with options to renew month by month or buy one or two years in advance "atlassian.com". That is the core commercial rule behind Jira billing. If you forget to cancel, the subscription renews for another term matching the current one.
The same terms also confirm free trials for Jira Cloud Standard and Jira Cloud Premium. In plain language, a free trial is useful only if someone on your team owns the billing reminder. If the trial converts and the refund window passes, getting money back becomes much harder.
Atlassian's terms say California law governs the contract and disputes go to binding arbitration in San Francisco, California "atlassian.com". For an everyday Philippine consumer, that does not mean you should stop using local remedies. For billing disputes involving a card, e-wallet, or a merchant transaction, your local bank process and DTI complaint route are still the practical first moves.
The more useful clause for ordinary users is the post-cancellation access rule. Atlassian says you can access the site for 15 more days after the subscription period ends, then the site is deactivated and data is retained for a period depending on the plan. That is the clause you should act on before cancelling, especially if your team has compliance or client records inside Jira.
Plan | Price (PHP) | Billing period | Main features |
|---|---|---|---|
Free | ₱0.00 | Monthly | Up to 10 users |
Standard | ₱1,500.00 | Monthly | Basic team features |
Premium | ₱3,000.00 | Monthly | Advanced admin tools |
Enterprise | Custom pricing | Annual | 800 plus users |
The figures above reflect the latest available pricing data in the research set, and Atlassian notes that pricing may change over time "atlassian.com". For a small Philippine team, Standard at ₱1,500.00 monthly is the first level where recurring billing becomes a real issue if nobody monitors renewals.
Among the listed public amounts, Premium at ₱3,000.00 monthly is the most expensive standard tier, while Free at ₱0.00 is the least expensive by definition. If your team has 10 users or fewer and mainly needs basic issue tracking, staying on Free or downgrading from Premium to Standard may be more sensible than paying for features nobody uses.
Enterprise is priced by custom annual arrangement and usually targets organizations with more than 800 users. If you are a smaller company paying for a feature-heavy setup you barely touch, cancelling and moving to a lighter tool can save a noticeable amount over a year. A team on Premium at ₱3,000.00 a month is already at ₱36,000.00 over 12 months before add-ons.
For users in the Philippines, the most relevant law is the Consumer Act of the Philippines, Republic Act No. 7394, with the Department of Trade and Industry as the consumer authority named in the research data. For online subscriptions like Jira, there is no general universal cooling-off rule that automatically gives you 7 days to reverse any online software subscription.
A 7 working day cooling-off period is more clearly associated with door-to-door or direct sales situations, not ordinary online SaaS signups. So for Jira, the practical reality is this: your strongest immediate protection usually comes from cancelling before renewal, staying inside Atlassian's refund window, and using your bank dispute rights if billing continues after cancellation.
If you cancelled and still got billed, gather evidence before complaining. Save the cancellation screenshot, invoice, bank or card statement, workspace name, and the date you lost access or tried to contact support. This kind of paper trail matters because many billing disputes turn on whether you can prove the exact cancellation date.
You can raise the complaint with DTI under RA 7394 and also start a payment dispute with your bank, GCash, Maya, or card issuer. If the problem is an unauthorized or continued charge, ask for chargeback instructions right away and mention the statement date because the common dispute window is up to 60 days. For Jira specifically, compare your renewal date with the date you clicked cancel so you can explain the timeline clearly.
The research data identifies DTI as the authority for this area. Use DTI for the consumer complaint side and your payment provider for the money recovery side. In practice, bank disputes often move faster than waiting for a merchant reply when the charge has already posted.
For official consumer information, use the DTI website and keep your complaint focused on dates, amounts, and proof. If Jira's terms mention California law and arbitration, do not let that distract you from the local steps that actually help a Philippine cardholder facing a recurring billing problem.
Overall sentiment in the available review set: 0 positive and 3 negative reviews out of 3 unique reviews. Based on that small but consistent sample, Jira's cancellation experience looks difficult rather than smooth, especially when billing ownership is unclear or support response is slow.
To stay balanced, Jira itself remains a powerful project tool with strong workflow features and broad industry adoption. The issue in these reviews is not product capability. It is billing friction, cancellation clarity, and refund rigidity.
Theme | Frequency | Typical example |
|---|---|---|
Charge after cancel | 2 reviews | Billing continued |
Refund refusal | 1 review | No credit issued |
Support frustration | 2 reviews | No useful reply |
Source | Rating | Number of reviews |
|---|---|---|
TrustPilot | 1 out of 5 | 3 reviews |
"I am extremely frustrated with Atlassian's billing and cancellation process. My subscription was cancelled on March 24, 2025, and have not used the service since. Despite this, payments have continued, and I am unable to access the account to cancel it myself." (TrustPilot)
"Automatic billing, zero usage, and no remediation. We requested cancellation almost immediately after renewal, yet were still charged approximately $5,000 [about ₱280,000]." (TrustPilot)
"Trying to migrate to Jira and wish I hadn't bothered, it's a total nightmare of site, the simplest of things they have made incredibly difficult." (TrustPilot)
A clean cancellation record can save you days of stress if billing continues. Before you click anything, save the current plan page, the renewal date, the invoice amount, and your workspace or site name. For a Standard plan that could be a screenshot showing ₱1,500.00 monthly, while Premium could show ₱3,000.00 monthly.
If you later ask for a refund or file a chargeback, the most useful documents are the transaction ID, invoice date, statement date, and proof that you cancelled before the next renewal. If the payment came through App Store or Google Play, save the store receipt because Atlassian may not control that billing record.
After cancellation, monitor the next statement closely. If a new charge appears, your evidence set should already be ready for DTI, your bank, GCash, Maya, or your credit card issuer. This is one of those cases where screenshots taken on the same day can make the difference.
A classic mistake is trying to cancel inside the Jira app when the actual subscription was purchased through App Store or Google Play. The result is simple and painful: you think the job is done, but the store billing keeps renewing. Always match the cancellation channel to the original payment channel.
A quick test is your receipt. If the receipt says Apple or Google, cancel there. If it is an Atlassian invoice, use my.atlassian.com and the Atlassian Cloud subscription list.
Another common problem is waiting until the charge date itself. Because Jira renews automatically unless cancelled before the current term expires "atlassian.com", leaving it to the last minute is risky, especially if the billing owner is not available or you cannot access the correct admin account.
A safer habit is to cancel at least 3 days before renewal and then capture the confirmation screen. This matters even more for annual plans, where one missed deadline can trigger a much bigger charge than a monthly plan.
Many users assume that if they cancel halfway through the month, Jira will return the unused half. Atlassian's published cancellation guidance says no credit is offered for cancelling before the end of a billing cycle "support.atlassian.com". That means unused days inside the current cycle are usually lost.
The same issue appears in complaints from users who renewed and then tried to reverse the charge after little or no usage. If you want a refund chance, act inside the stated refund windows, not after them.
One review described a cancelled subscription followed by continued payments and no account access, which is exactly the situation where screenshots become vital (TrustPilot). If you do not keep the confirmation page, a bank dispute becomes harder because you may not be able to prove when the cancellation happened.
Save at least one screenshot, one invoice, and one statement entry. Those three items usually form the minimum useful bundle for a complaint.
Method | Notice period | Fee | Difficulty |
|---|---|---|---|
Web/account | Before next billing | No fee found | Easy |
App Store (iOS) | Before next billing | No fee found | Medium |
Google Play (Android) | Before next billing | No fee found | Medium |
Registered mail | 5 to 10 business days | No fee found | Higher, best proof |
Each route fits a different situation. Web account cancellation is the normal path for direct Atlassian billing, while App Store and Google Play only apply when the subscription was bought through those stores. Registered mail is slower but can help if you need a formal record of your notice.
No cancellation fee or early termination fee was found in the terms data provided. The bigger financial risk is not the cancellation itself. It is forgetting the renewal date or assuming a refund will be automatic after cancellation.
Right after cancellation, look for a confirmation screen or message in the billing portal and save it. Then check whether the subscription status shows a pending end date rather than active auto-renewal. Add a calendar reminder for the day before and the day after the next expected billing date.
If your plan was direct with Atlassian, also watch for any confirmation email linked to the billing account. If none arrives, that does not always mean failure, but it is a reason to re-open the billing page and confirm the status manually.
Monitor your bank, card, GCash, or Maya account through the next statement cycle. If an unauthorized or continued Jira charge appears, contact the payment provider immediately and ask for the dispute or chargeback process. In the Philippines, cardholders commonly have up to 60 days from the statement date to dispute a transaction under BSP-related practice.
For the consumer complaint side, DTI handles online subscription issues under RA 7394. Use your cancellation screenshot, invoice, and statement entry as evidence. This is the point where being organized pays off.
If you are cancelling because Jira feels too heavy or expensive, Asana is often easier for non-technical teams and starts with a free basic plan plus paid plans from $10.99 (about ₱615) per user monthly. Smartsheet suits spreadsheet-friendly teams that want dashboards and automation, while GitScrum starts at $8.90 (about ₱499) per user monthly and may appeal to teams that want a lower-cost agile workflow option.
These are not perfect substitutes for every Jira setup, but they can reduce administrative friction for smaller teams. Choose based on the features you actually use, not the longest feature list on paper.
If you want a physical contact point for record purposes, use this address:
This address is useful for formal correspondence, but Jira subscription cancellation itself is handled online through Atlassian account systems rather than by walk-in or postal processing.
Use the Manila address if you need to send supporting documents or create an additional paper trail after an online cancellation problem. Do not rely on it as the primary method for stopping renewal because the verified cancellation process is through my.atlassian.com, App Store, or Google Play depending on how you subscribed.
If your goal is speed, the online route is the one that actually controls billing. If your goal is evidence, a postal record can support your case alongside screenshots and bank statements.
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.
Written by Anton Gonzales
Former postal advisor · 3 years experience
Former postal-services advisor and e-signature specialist, I have been writing for Postclic for 3 years to demystify legally binding mail for everyday users.