We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
The notice I got in Thunderbird led me to the wiki page and I can confirm that the API endpoint of bugs.kde.org is just https://bugs.kde.org/rest.
https://bugs.kde.org/rest
For instance, I could run
curl https://bugs.kde.org/rest/bug/300000
...to fetch the details of this bug. And they also allow generating API keys at https://bugs.kde.org/userprefs.cgi?tab=apikey
The text was updated successfully, but these errors were encountered:
hello,
thanks for looking into this!
could you submit a pull request to modify the following table? https://github.com/protz/thunderbird-conversations/blob/master/content/stub.compose-ui-bz.js#L49 I believe the keys are the value of the X-Bugzilla-URL and the values are the API endpoint... thanks!
Sorry, something went wrong.
@protz There you go #1272 For some reason they are not using https in in the email header field 🤔
We're going to be dropping the close bugzilla integration as it doesn't seem that useful and adds complexity we don't want to support at the moment.
Successfully merging a pull request may close this issue.
Hi,
The notice I got in Thunderbird led me to the wiki page and I can confirm that the API endpoint of bugs.kde.org is just
https://bugs.kde.org/rest
.For instance, I could run
...to fetch the details of this bug. And they also allow generating API keys at https://bugs.kde.org/userprefs.cgi?tab=apikey
The text was updated successfully, but these errors were encountered: