Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3489 Ideas

    Link Draft ArticlesSubmitted

    The problem: In the Help Center, you cannot link to a draft article. Internal links to unpublished articles are impossible because draft articles have no URL — so cross-referencing between two drafts can't be done until one of them is published.Example: I'm writing Article A and Article B, both in draft. Article A contains "For more details, click here," which should link to Article B. Because B is unpublished, there's nothing to link to. My only options are to publish B before it's ready just to obtain a URL, or publish A with a placeholder and remember to come back and fix it later.Why the current workarounds are risky:1. Publishing early exposes unfinished, unreviewed content to customers and gets it indexed by search engines.2. Placeholder links get forgotten, leaving "click here" dead-ends in live articles.3. Coordinated launches are painful — shipping a new feature with several interlinked articles means publishing them in a careful sequence and then re-editing each one to add the links, instead of preparing everything in draft and publishing together.The request: Let authors link to draft articles while editing. The link doesn't need to resolve publicly until the target article is published — it just needs to exist internally so the content is complete and correct on publish day. Bonus: a warning indicator if an article is published while it still links to an unpublished draft.This would make large documentation projects and product-launch docs dramatically easier to prepare, improve collaboration between authors, and remove the need for premature publication. Thanks for considering!Please let me know if you have more questions.

    Christian S12
    Christian S12Connector

    Ability to Associate a JIRA Ticket with Multiple Intercom TicketsSubmitted

    Currently, the integration allows updates to statuses and comments from JIRA to Intercom, which works fine. However, there is a limitation where a JIRA ticket can only be associated with one Intercom ticket at a time, which creates some inefficiencies in workflows.Issue: We track bugs that are worked on in JIRA through Intercom tickets. However, with the current limitation of the JIRA for Tickets app, we are only able to apply one JIRA ticket to a single Intercom ticket. This is problematic because it doesn't reflect the reality of how multiple customer support tickets may be related to the same JIRA issue as well as allow the automation for JIRA ticket status updates to be sent to Intercom and out to the customer via the custom statuses feature. Request: I would like to request an enhancement to the JIRA for Tickets app, allowing users to associate a single JIRA ticket with multiple Intercom tickets at once. This feature would work similarly to how the JIRA for Cloud app allows for multiple associations, and would significantly improve workflows for teams who track related customer support tickets across different issues in JIRA.By adding this capability to the JIRA for Tickets app, teams would be able to link a JIRA ticket to multiple customer support tickets, ensuring a more accurate representation of the work being tracked and updated across all associated tickets.