Levente Szabo _Midori_ Atlassian Partner

@Celia.Bras The native steps are already covered above, so I’d add the option that doesn’t depend on where Jira moves its own export menu next. Better Excel Exporter has an Excel Export Center that you open from the Jira left bar under Apps. Pick “Export work items from a JQL search”, paste the query you run in the All…

@Mohit Verma I think the “automated, year by year” part decides the tool here, so I’d start from what a one-off export can give you and then add the schedule on top. Better Excel Exporter makes a native .xlsx from an Excel template, so you don’t get a CSV that you have to clean up afterwards. For your column list: Jira…

@Kyle Zuo Jira Service Management measures SLAs per ticket: each one is met or breached against a goal, on a calendar. It has no native concept of a contract period, an attainment threshold, a credit tier or a cap. So the credit itself is always calculated outside native JSM, and the real question is how reliably the SLA…

@Kim Clark I’d add a note on the “for analysis” part, because that’s where the CSV route usually takes the most time. Each entry lands in one text cell (comment;date;author;seconds). Before you can total anything, you have to split those cells, turn seconds into hours and build the pivot yourself. Better Excel Exporter has…

If the retired dashboards can be rebuilt as regular Jira dashboards (Created vs Resolved, Pie Chart, Two Dimensional Filter Statistics, the JSM Filter Counts gadget and so on), there is a third route that keeps the Monday PDF: Better PDF Exporter exports a whole Jira dashboard to PDF, charts included. It is the only…

@Jesus Nieto I’d split the problem by where the values come from. A good share of what teams put into Page Properties is lifecycle metadata: owner, status, review date, when the page was last really updated. Those fields drift because someone has to type them. I think they’re better calculated than entered, and then only…

@Nicoleta Mircea I’d add one point on timing. Most of those days go into rebuilding the evidence after the auditor asks for it. If the evidence is captured while the change moves through the workflow, the audit request turns into a search over files that already exist. Two ways teams do this with Better PDF Exporter: For…

@Neha since {{lookupIssues}} can’t read time tracking on Data Center, one way to keep the report inside Jira Automation is to have the rule generate the report file instead of adding up the total in a smart value. With Better Excel Exporter and the free Better Excel Automation app, the rule needs two changes: Keep your…

@Anna Wilson_3pwqr8 , I think the part these workflows tend to leave out is the end of the cycle: what happens to a page when the reminder goes out and nobody acts on it. Without that step the review queue only grows, and stale pages stay in search right next to the current ones. So I’d treat ownership, reminders and…

@Masa with 20+ organizations, I think the data itself is rarely the problem. The 1 to 3 days go into rebuilding, reformatting and sending the same report by hand every month. So the setup to aim for is one you build once per customer and then leave alone. That’s the gap Midori covers with two apps: Better PDF Exporter…

@GAdkins I think the part of the Time Tracking report worth keeping is the one you describe: for each work item, how the original estimate compares with the time actually logged. That comparison only needs the time tracking fields side by side, so it can outlive the report without anyone cobbling worklogs together by hand.…

@eb FWIW, I think a monthly worklog export with organization, reporter, assignee, and comments is a fair thing to expect without writing code, so here is a route that needs none. Better Excel Exporter for Jira adds Excel export views to the work item search, so you can keep the saved filter and the columns you already have…

@AGASTYA SHARMA I think the suggestion to archive outdated pages is correct. The question that follows is how you decide which of two disagreeing pages is the outdated one, because that is the part Rovo can't do for you. Conflicting pages usually share a root cause: nobody owns them and nobody is asked to confirm they are…

@Krishna Modem the checks above cover the agent configuration well. If the old data still shows up after you have narrowed the knowledge and tested in a fresh chat, the likely cause is copies: an earlier version of the same table in another space, an export, a duplicated page. The agent can read all of them, and deleting…

@Mini Channanathil your three use cases match what the audit log shows, and I think the practical way around the missing page ID is to stop depending on knowing which pages came from an AI tool. A page created through MCP is a normal page created by that user, so you can put every page in the spaces where AI drafting is…

@Justine on who should own a KB article, the practice that holds up best in our view is to treat creator and owner as two different roles: the creator documented the fix once, the owner is accountable for the article staying true. For application-specific how-tos that usually means the owner is the person or team who owns…

@Harish Babu N Babu the part of your question that maybe hasn't been covered yet is the "if no one has used it in 6 months", meaning views rather than edits. Native Automation works from the last edited date, so a page that is read every day but untouched for six months looks the same as one nobody opens. Telling those…

Hi @nboreddy, I think the piece still open is the Jira Automation side of your question specifically, since neither reply confirmed that part yet. I'm one of the people building Better PDF Exporter and Better Excel Exporter at Midori. Between the two, we cover the PDF and Excel half of your format list plus the automation…

Adding to what Aron shared above, since you mentioned this is for regular knowledge maintenance rather than a one-off migration: the fields you listed (Status, Created/Updated Date, Creator, Last Modifier) are exactly the signals that go stale again the moment you close the spreadsheet. So I think the audit works best as…

Hi @Kasyah Sydnor, on top of what's already covered here (Page Properties, Databases, or Properties for the metadata schema), the aspect that's often forgotten is the content lifecycle itself. Effective Date, Last Reviewed, Next Review: a field can hold each of those, but it won't chase down the owner, flag a policy that…

Yes, this is doable. Native Jira/Xray export won't give you step-level detail in bulk, but Better Excel Exporter for Jira handles it: * Collect all your Tests in Issue Navigator (a JQL query works fine for 500+ at once). * Add the "Manual Test Steps" field as a column. * Use the app's "Better Excel" export option. You get…

@erica_bogosian I understand you are trying to solve your requirement with Automation for Confluence, although the experience of many of our enterprise customers is that it is not fully up to the task of managing content lifecycle at scale. Our team at Midori has been working with enterprise teams for 15+ years (like…

@Brandi Guess As I mentioned in the other thread, I wanted to discuss an idea and sent a LinkedIn invitation to connect. Can you please see if you can find it now? On the page status topic: you are not alone with that opinion. The experienced team at nCino wanted to implement its content lifecycle management strategy using…

Hi @Alexandr By looking at our support desk, Kaviraj reached out afterwards and continued the consultation with our team towards a solution. I encourage you to reach out to us as well with your specific question, so we can take a look and provide the right advice.

@Eleni Georgiou Are you using Better Content Archiving for Confluence Cloud to manage your page statuses professionally? The screenshot in your question is actually from the app's tutorials. If yes, then one option to turn off statuses is to exclude certain pages from lifecycle checks. You can exclude entire spaces or just…

@Gwen As mentioned before, Confluence page status can play a super important role in an automated content lifecycle management strategy, triggering notification emails for stale content or automatically archiving or deleting pages. One thing you run into when looking more into built-in statuses is that there are only 5 of…

@Tarun As it was mentioned, your question has 2 parts: using a commit message template and enforcing/validating that commit message at commit or merge time. 1. Commit message templates (Git native) Git itself doesn’t natively enforce commit message patterns on the server, but you can use local Git commit templates to…

@duncan.wraight You can achieve this using Better Commit Policy Connector for Bitbucket Cloud which integrates with Jira Cloud via Better Commit Policy for Jira Cloud (you need both apps) It enforces rules directly in Bitbucket Cloud to: Require Jira work item keys in commit messages and/or pull request titles Validate the…

@Karen, and all those interested in advanced Bitbucket Cloud pull request rules, The mentioned cloud versions of Better Commit Policy for Jira and Bitbucket Cloud are now available! If you need a reliable and scalable way to enforce Jira work item keys only on certain branches, a custom solution is required. One approach…