Skip to content
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

Jira #567

Open
BNYBLN030 opened this issue Sep 13, 2017 · 5 comments
Open

Jira #567

BNYBLN030 opened this issue Sep 13, 2017 · 5 comments
Labels

Comments

@BNYBLN030
Copy link

How Is the correct way to Connect jira with seccubus?
The documentation Is very Slim ...:(

@MrSeccubus
Copy link
Member

The only JIRA integration we currently have is that you can make turn the external reference for an issue clickable.

To do this find this section in you config:

	<tickets>
		<url_head>https://jira.atlassian.com/browse/</url_head>
		<url_tail></url_tail>
	</tickets>

This will turn external reference test-1 into a clickable link to https://jira.atlassian.com/browse/test-1

@BNYBLN030
Copy link
Author

@seccubus okay i unterstand, that means that no Data/findings Push automaticly to jira ??

@MrSeccubus
Copy link
Member

It's high on my list of things I want to do, but I have limited development capacity.
Would be great if somebody could help.

@Ar0xA
Copy link

Ar0xA commented Nov 20, 2017

ok, I'll add it. How's this sound:

  1. I'll start with expanding the tickets with the option for an API-key to interface with jira. My suggestion would be to create a config option <ticket_type>JIRA</ticket_type> and <api_key> config options. This way other ticket API interfaces could be made at a later point.

  2. I'll then add the ability, in the gui, create an automatic ticket of the selected (one or more) issues. This will include checking if there's already a valid external reference ticket. If a ticket already exists, it will not do anything.

  3. I'll add the ability to, once a scan is finished, to automatically create a jira link for findings above a certain level <min_ticket_level> or something similar. This will include checking if the finding already has an external reference or not.

  4. everything else.

or 2 and 3 reversed..whichever feels easier at that point :)

Obviously doing this in my spare time, so might take a while, be patient.

@MrSeccubus
Copy link
Member

MrSeccubus commented Dec 8, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants