Monika Ambrozowicz_Seibert_ Atlassian Partner

Hi @Jesus Nieto, our clients use a marketplace app called Properties. As you said, Page Properties do the job with collecting page-attached metadata that rolls up into reports, but the fields are free-text only (so no dropdowns, date pickers, or user pickers…), and keeping the schema consistent across many pages relies…

Hi @Jaspreet Singh, you've already got good answers to your questions - Jira does have some standard templates, and additional enhancements can be done with Jira Automation. One thing that native Jira doesn't handle out of the box is standardizing the structure of individual user stories as your team creates them. Jira's…

Hi @William Rudy, unfortunately the Page Properties macro is the Cloud version of Page Properties on Server/Data Center, I don't think you can find something else in native Confluence. It is also true that it is limited, it's a simple small table with no field types, no dropdowns, no date pickers, no user pickers… If you…

Hi @Nathan Unsworth, I can see two possible reasons behind this issue: Either you have hit the limit of pages displayed, because the native Content Properties Report macro doesn't show unlimited number of pages. Or if your pages span across multiple spaces, the report's space scope might not be set to cover all of them,…

Hi @Kranthi kumar Girri 👋 Unfortunately, Jira Cloud doesn't offer a native rich text custom field type. The built-in Paragraph/Text Area field is plain text only and caps out at around 30k characters, but the editing experience is nowhere near the Description field: no formatting toolbar, no inline images, no hyperlinks.…

Hi @Kasyah Sydnor, Confluence can absolutely work as a policy management platform, and many teams use it this way. Out of the box, you can create a page per policy and use the native Content Properties macro to add metadata like the owner, status, or effective date. The limitation is that native Content Properties is a…

Hi @Chris, I think it makes a lot of sense to centralize as much as possible into Confluence. Atlassian's focus seems to be bringing Jira and Confluence closer together, especially thanks to Rovo; and finally there are marketplace apps that create links and fill the gaps in native capabilities. Confluence databases are…

Hi @WP, from what has been shared in that article and other community discussions, the native colored labels feature in Jira Cloud does currently assign colors automatically and randomly rather than letting you pick them yourself. Whether that's a permanent design decision or a temporary state hasn't been publicly…

Hi @Ggy, on the scheduling side, Jira Automation (native, built into every Jira Cloud plan) can handle the recurring trigger. You can set rules to fire on a schedule (monthly, quarterly, annually) that create work items automatically. This works well for the cadence problem. The native Set to recur workflow is very easy to…

Hi @김대현, there is one more thing I have in mind. The notification system was originally designed with single-user picker fields in mind, so maybe the fact you're using the multi-user picker fields causes the problem? I would replace it briefly with a single-user picker just to test if it works. If you're open to a…

Hi @Kathryn Lee you've already got quite a lot of useful recommendations, but I'd like to add one more so that you have more options to compare :) Templating.app does exactly what you described. It lets you define multiple work item templates: one for 'Weekly Report Story', one for 'Monthly Report Story', etc., each with…

Hi @Andreas Gandrup you're right that native Jira automation doesn't support a "form opened" trigger. Automation rules are reactive (they fire after an issue exists), so there's no built-in way to pre-fill fields before the user submits the creation form. I know you mentioned you'd rather avoid marketplace apps. However,…

Thanks @Léon Pluister, from you described, I'm sure that AutoPage will meet your needs. If you have any questions please feel free to ask them via our support portal: https://coderay.atlassian.net/servicedesk/customer/portal/1 or book a demo if you'd like to get a personalized tour: https://calendly.com/coderay 

Hi @Léon Pluister, unfortunately, there's no native way in Jira Cloud or Confluence Cloud to trigger page creation from a specific Confluence template when a Jira issue is created or updated. The closest native option is the "create Confluence page" button from Jira, but it doesn't use Confluence templates, the page is…

Hi @Rik Kochuyt! As others have already suggested, the default native approach here is the Content Properties macro (sometimes still called Page Properties macro), which lets you add a key-value table to a page. It works, but all values are free text - there's no date picker for the end date, no user picker for the page…

Hi @slucchesini, you've got quite a lot of great recommendations already, but I'd like to add one more for you to compare with the others :) It's called Awesome Custom Fields (full disclosure: I'm affiliated with the team behind the app). It includes a "Time in Status" field (next to 20+ other super useful fields, like a…

You're not missing anything @Pat Flanakin Jira Cloud doesn't have a native project clone function. The closest thing is the CSV export/import path you're already using. I know that buying a 3rd party app is not your preferred solution but, unless I'm wrong, there aren't any other efficient workarounds. If you'd consider an…

Hi @Anita Bennett, for flagging issues as 'low hanging fruit' or filler candidates, you have a few native Jira options worth considering before reaching for a Marketplace app. A single-select custom field with one option (for example, 'Candidate for filler') works exactly as you described. It is reportable via JQL and…

Hi @Mikel Whipple, the native formula field in Jira Cloud does support some date calculations, but the pattern you need isn't currently available - it is limited to calculations between two existing field values, not between a field and the current timestamp. So you're not missing anything; what you're trying to do just…

Hi @Chan_ Renee, I have a solution for you if you're open to Marketplace apps. AutoPage lets you define automation rules that generate (and keep in sync) Confluence pages from Jira issues using Confluence templates you build with special placeholder macros. The one that's directly relevant to your problem is the…

Hi @Abilash did you manage to solve your issue with the form? If you couldn't achieve what you wanted to, I have a suggestion but it requires installing a Marketplace app. Didit Checklists for Jira allow you to create the decommissioning checklist once as a reusable template, organized into sections like 'Data & Pipelines,…

Hi @Anders Ankartoft, this is actually a common frustration - Jira's native 'create a Confluence page' automation action is essentially fire-and-forget. It can create the page, but there's no built-in way to dynamically embed the originating Jira issue key or link into the page content at creation time (beyond manually…

Hi @Kustagi Suma I've just come across your question, have you found your solution already? One of those suggested here or another one? If you're still looking for the right approach, I wanted to suggest that Jira's native cascading select field is worth considering first. You can create a single cascading select custom…

Hi @Jamie Knight, Confluence's native page ownership is limited to a single user - there's no built-in way to assign a team or group as the owner, and I'm not aware of an existing feature request that has gained significant traction on this specifically. Having said that, and also as someone who manages quite a lot of…

Hi @Gretchen, @James Gamble and @Germán Morales have explained the issue already. This happens frequently when chaining issue-creation actions in Jira Automation because the project context or the issue type ID isn't available or is being referenced incorrectly. If you are open to a third-party app, Templating.app has…

Hi @Julia Thummerer, as @danylo_iliukha suggested, you still need a workaround, as the release date is not yet known. If you are open to marketplace apps, I would like to suggest Awesome Custom Fields. It includes an Advanced Formula field type that lets you build calculated fields driven by other field values, without…

Hi @Ash H_ I'm not sure if by a placeholder text you mean a greyed-out hint or a pre-populated structured content in the description field. If you mean the latter (or both solutions are ok for you) and if you are open to installing a marketplace app, Templating.app has Description Templates. They pre-populate the…

Hi @Veronica Rodriguez, I've come across your question and although I can see you've already got a highly relevant answer, there is something I would still like to add. For what you need (automatically create a Confluence page from Jira using a predefined structured template), I feel like there is a better solution than…

Hi @sravani vennapusa, I've just come across your post and I wanted to add another suggestion. The closest native workaround for your need is using Jira Automation: you can create a rule that triggers on issue creation, reads the issue ID or a counter variable, formats it as a zero-padded string, and writes it to a text…

Hi @Paul Marachlian, afaik it is not possible. JSM Playbooks are designed more as guided task lists for agents, so they don't natively integrate with Jira workflow transitions as enforceable gates. So to block a transition until work is done, you'd need to connect Playbooks to something the workflow engine can actually…