-
Notifications
You must be signed in to change notification settings - Fork 120
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] Project name should be in project.json, not in mordred.cfg #122
Comments
Ooo perhaps this could be one that, with a little bit of help and pointing me in the right direction, I could try taking a stab at preparing a PR for? |
Of course! If you want, have a look at how |
I've filed #125 first so I can figure out how to run the tests first before I attempt to change anything :) |
I think I will take a closer look at this issue. I would also require that we expose some manner of authentication, e.g. Basic Auth, for JIRA (our corporate JIRA instance requires either OAuth or Basic Auth). |
I am able to get perceval to talk to my corporate JIRA instance and get past basic auth, etc. I promise to look into this issue soon 😄 |
Question: would configuring the JIRA backend via the mordred config to a specific JIRA project somehow result in the issues pulled in from that JIRA project be associated with the correct (git/github-backed) project defined in projects.json? Or would that functionality be part of the changes we want to implement in this issue? For example, we have an internal project called RSP. I could set the mordred config file as follows:
Then my
Would this setup be sufficient for the JIRA issues under the RSP JIRA project to be associated with the RSP project as defined in |
It looks to me like some tests in sirmordred pass command line flags/parameters via the main (URL?) string inside However, when I try this w/ JIRA (as in your original example above @jgbarah), I get errors as it seems the perceval JIRA backend assumes everything in the string to be a URL. I dug through the code a bit, and I'm not sure whether this would necessitate a change in either perceval or mordred, but perhaps grimoire_elk? Here's my reasoning:
So my thinking is: why not implement the Let me know if that makes sense and I can open a new issue in elk and attempt to put a PR together. |
Sorry for the late reply! The current implementation should be fine, in a nutshell all data stored in a Jira is reflected to the raw index, while the enrichment phase can be set up to enrich only some projects. To achieve that, you should have a projects.json like the one below (more details about the
|
Perceval Jira backend allow user to specify a project:
In this case, only issues for that project will be retrieved from the Jira API.
The current way of specifying this for Mordred is in
mordred.cfg
:But this is weird, and allows only for a single project to be filtered. This should in fact be in
projects.json
, and should be specified in a way that any list of projects from the Jira API endpoint are specified. For example, it could be like:See some more details in a recent question, #121.
The text was updated successfully, but these errors were encountered: