-
Notifications
You must be signed in to change notification settings - Fork 35
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
how to install/use? #2
Comments
I'm sorry for the documentation, it really is not comprehensive enough... So, the intended way ejira is used is not to enable Then you run the command Then, there are multiple ways to interact with the tickets.
The package does not have any default bindings yet, I use evil personally. I do not expect everything to work out-of-the-box yet, since you are probably the first one after me who is taking the library to use. It has also never been tested with any other JIRA server, or any other workflow. But let's see if we can you up and running. Feel free to send more comments if something does not work, something works weirdly or something is unclear. |
When I execute |
Can you enable debug-on-error |
the only part i understand is the 401 ^^ does it mean i have no access to the api?
i have no idea how to make this code look pretty, sorry |
No problem, I can manage with this one. The issue seems to be that the HTTP response does not have a status code (it gets set to nil and thus the comparison to 401 fails). So the 401 here is not the actual status code you receive, but one we compare it to. Maybe it times out? How long does it take for the command to fail? Double check that
If that does not work, your JIRA instance might have REST api disabled, ask your administrator. Edit: FYI, I was able to reproduce the same error by making my |
hmm ... strange ... I login in my browser to jira and go to
but in my init.el |
The password is asked before the actual request is made so it is not a quarantee that the login was successful. Easy way to check if the login works is to evaluate
Parentesis around the If an active sprint is found and it is successfully parsed, then it tries to fetch the actual issue data. You can also pull the newest changes I made yesterday, it should give a bit better error messages for failed API calls. |
Well |
You can then try the
The cookie expires in a short while, so you most likely need to renew it by calling You can try with several search queries: |
Hi, Also trying to get this working. Simply cloned the repo and tried to initialize with the use-package
And I'm getting the following error:
|
language-detection.el is required by ejira. You can install it from melpa. Other dependencies are ox-jira, s, cl-lib and request. |
Already solved. Was a bug on my configuration! |
How does one find out what the custom fields should be? |
The way I did it was to pull the json of one of the tickets from the rest api with Postman and then manually check what is the name of the field containing the desired information, for example the epic key. I don't know if there is a way to extract this mapping directly from the API. |
your project looks very promising, but i dont know if i did something wrong or just our jira is messed up.
i added cloned your repo under ~/.emacs.d and added to my init.el under ~/.emacs.d
(add-to-list 'load-path "https://ourjira.com")
Then i continued with the setq-part from your example config followed by require 'ejira and 'org-agenda
At the beginning there were some errors because of missing packages (e.g. language-detection) but now there are no errors at the start of emacs. With M-x i am able to enable ejira-mode (when i'm in an org-file) but then i dont see the point, how to start?
The text was updated successfully, but these errors were encountered: