-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scan specifica Confluence Pages & JIRA Tickets Only. #29
Comments
Hi Maneppagolmanju, thanks for your suggestion. This is actually on our roadmap for future releases. There has been previous discussions about this feature (see this previous issue) and I started drafting something (see this branch with a draft code), however I could never get to a point where the implementation would cover all cases. The ideal solution seems to point to a strategy where you map the target (Jira, Confluence, Asana, etc) and create a JSON like file where you can add remove workspaces/tickets for future scans. The mapping file would be used as input so you can customize the ticket list (in a structured JSON format) that you wnat to scan. |
Hi @Maneppagolmanju, I just wanted to let you know that I have a new PR #31 out that implements a solution for this issue. Please let me know if it addresses your use cases. |
To scan specific Confluence pages or Jira tickets, amke sure you are using n0s1 version 1.0.25 or earlier. Create a map, edit the map to have only what you want to scan, save it and run a scan. For instance: python3 -m pip install --upgrade n0s1
n0s1 jira_scan --map --map-file jira_map.json
vi jira_map.json
n0s1 jira_scan --map-file jira_map.json |
Hi @blupants Thanks for rolling it out. I will explore and let you know. |
Thanks for taking the time and looking at this. If you notice the map file is too big and/or taking too long to be generated, you might do the "quick mapping" instead. Use the flag |
Hi All,
Can we have functionality to provide input to scan specific pages in Confluence page, list of JIRA tickets from the input?
Idea is to scan tickets/pages that were updated after the last scan instead of scanning entire spaces again and again.
We can use this approach to near real-time monitoring.
Regards,
Manju
The text was updated successfully, but these errors were encountered: