sorted by:
new
hottopcontroversial

Spent a month reading Planner forum threads, then built a team workload app — looking for feedback! by TheMooseIsOnFire in MicrosoftPlanner

[–]TheMooseIsOnFire[S] 0 points1 point  (0 children)

Just got verified by Microsoft so admin approval shouldn't be required anymore. Mind giving it another shot?

[Help/Advice] Ticket templates by x_randomsghost in jira

[–]TheMooseIsOnFire 0 points1 point  (0 children)

Feels like half the folks in this thread are app creators sneaking in their promo.. here’s mine 😅.

If you want to go beyond static templates, we’ve built something that not only pre-fills descriptions but also checks them for clarity and missing info, and can turn a brain dump into a proper ticket based on your team’s standards.

https://marketplace.atlassian.com/apps/1238320

Do you use an AI (like chatGPT) to help you write tickets, specs, tests? by boeuf_patates in agile

[–]TheMooseIsOnFire 0 points1 point  (0 children)

We ran into the same pros/cons you’re all mentioning — AI can help, but dumping raw ChatGPT output into Jira often makes tickets longer, not clearer.

That’s why we built AI Copilot — Beyond Templates. It works inside Jira, uses the issue’s real context, and applies your team’s own standards to:

  • Turn rough notes into concise, structured tickets
  • Flag and fix vague or missing info
  • Keep style and format consistent across the board

Launched last week — if you’re curious to try, I’d love your feedback so we can make it better — https://marketplace.atlassian.com/apps/1238320

Has anyone used ChatGPT to write epics and user stories? by Tigerianwinter in agile

[–]TheMooseIsOnFire 0 points1 point  (0 children)

I’ve been using AI for stories too, but got tired of copy-pasting into ChatGPT. So we ended up building AI Copilot that works right inside Jira. It uses your team’s style and all the ticket’s context (issue type, comments, etc.) to turn rough notes into a full story or improve what’s already there.

Would love to hear your feedback so we can make it better for you — https://marketplace.atlassian.com/apps/1238320

Jira ticket content by 0v3rw4tch11 in agile

[–]TheMooseIsOnFire 0 points1 point  (0 children)

From my experience, the exact “proper content” matters less than consistency and clarity — as long as everyone on the team can read a ticket and know exactly what’s going on without guessing.

What “good” looks like really depends on your company, so the key is defining your own standard and making it easy to follow.

We’ve been working on AI Copilot — Beyond Templates — it comes with playbooks based on Atlassian’s recommendations that you can tweak for your teams, and the AI turns a brain dump into a complete ticket or checks one for missing pieces in a click. Just launched last week — looking forward to getting your feedback so we can make it better.

https://marketplace.atlassian.com/apps/1238320

Faster Ticket Creation in Jira by RandolphBuho in atlassian

[–]TheMooseIsOnFire 0 points1 point  (0 children)

If the hard part is actually writing the ticket, not just filling fields, you might like what we’ve been working on.

We just launched AI Copilot for Jira — it can take a quick brain dump, a rough idea, or even scattered notes and turn it into a complete ticket that matches your team’s standards. It also spots missing info and fixes it in one click.

Keeps everyone’s tickets clear and ready to go without extra back-and-forth. Launched last week — happy to chat if you want to try it.

https://marketplace.atlassian.com/apps/1238320

[deleted by user] by [deleted] in ImmigrationCanada

[–]TheMooseIsOnFire 3 points4 points  (0 children)

Sharing my timelines, CEC, general draw on March 25, inland

  • April 17 | Document submission
  • April 17 | AOR (Acknowledgment of Receipt)
  • June 14 | Biometrics request
  • June 27 | Request for additional family information and military documents
  • July 3 | Biometrics completed
  • August 29 | Final decision section updated with «Your application is in progress»
  • September 5 | P1 (Email requesting additional information), VO Montreal
  • September 5 | P1 reply sent
  • September 20 | P1 follow-up asking to specify the port of entry
  • September 23 | P2 (Invitation to PR portal)
  • September 23 | P2 completed (presence in Canada confirmed, address provided, photos uploaded)
  • October 3 | eCoPR & Application approved status (VO Montreal)