Open archashaji1 opened 2 years ago
Hi @archashaji1 !
This sounds like a functional thing, I would suspect your JIRA is expecting a certain status or a certain field to be containing the appropriate value for the ticket to be in the "active" sprint.
I would suggest that you check out with JIRA admin what is expected to be set for that to happen? (it might be a custom field for example, or a certain assignee or reporter)
Guilhem
Hi,
Thank you for the response.
I believe the custom field sprintId will help me in adding to the active sprint. But I'm not sure how to specify that custom field value in the manual SPL query which I'am using to create ticket
This is the screenshot of how the custom field is structured:
The manual SPL query that I'm trying to use to create ticket in Jira is as follows:
|makeresults | sendalert jira_service_desk param.account="JiraCloud" param.jira_project="SORTest" param.jira_issue_type="Task" param.jira_priority="Low" param.jira_description="From splunk" param.jira_summary="Test ticket" param.jira_labels="Jira" param.jira_assignee="61xxxxxx5" param.jira_reporter="61xxxxxx5" param.jira_customfields = "{\"customfield_10003\": {\"id\": \"4137\"}}" param.jira_customfields_parsing = enabled
Let me know if any more details required.
Much Appreciated, Archa
Hi @archashaji1
Have you made any progress on this one?
Guilhem
Hi,
The Jira - Splunk integration is working fine with this addon. However, currently when I create ticket via this addon, it is found on the backlog. I have to log into Jira to move it to active sprint. It would be convenient if there is a configuration whereby creating a new issue is automatically placed on the current active sprint.
Let me know if it is possible my any means.
Regards, Archa