How do I launch ngx-jira-issue-collector in a separate browser tab rather than a modal?

Other Questions Jira
1

I want ngx-jira-issue-collector to open in a new tab instead of a modal. Field auto-fill and closing issues remain with the direct URL approach.

export const jiraSettings = {
  endpoint: 'JIRA_BASE_URL',
  key: 'issue456',
  defaultValues: { title: 'Ticket title' },
  fetchValues: () => ({ description: 'Extended explanation' })
};

<div>
  <button (click)="collector.openTab()">Launch Collector</button>
  <jira-collector [config]="jiraSettings" #collector></jira-collector>
</div>
2

hey have you tried using window.open() instead of triggering the modal? might need to rewrite some of the initializaition logic, but its workin for me.

3

I have modified the collector’s launch method to open a new tab using window.open while preserving the configuration for field auto-fill. The key was to expose the URL generated by the collector and then call window.open with this URL. It required minor adjustments to ensure that query parameters were properly appended and that any state from the modal approach was migrated. This approach worked reliably after device-specific tests and has the advantage of separating the context without interfering with the module’s initialization.

4

In my experience, altering the launch behavior of ngx-jira-issue-collector to open in a separate tab required a few modifications in how the URL parameters were handled. I ended up creating a custom function that constructs a URL based on the collector configuration and then calls window.open with that URL. This approach gave me better control over the routing and ensured that all field pre-population worked correctly while isolating the collector in a new browser context. It also allowed me to debug the issue more clearly by separating concerns.

5

hey, i tried making a hidden anchor with target=‘_blank’ that uses the collector’s URL directly. it simplified the process and kept autofill working. you might need to tweak a bit if state issues crop up. cheers!

6

In my implementation, I bypassed the modal by intercepting the URL configuration generated by the collector and then directly calling window.open with that URL. I did so by creating a small service that wraps the default collector functionality. The service extracts the necessary configuration while ensuring that auto-fill works. This method demanded adjustments for URL encoding and query parameter handling, but once set up, it provided a clean separation of contexts without interfering with the existing initialization. The approach has proven reliable across different browsers and scenarios.