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

Display open issue count for JIRA filter #4426

Open
guusdk opened this issue Jan 5, 2024 · 4 comments
Open

Display open issue count for JIRA filter #4426

guusdk opened this issue Jan 5, 2024 · 4 comments

Comments

@guusdk
Copy link
Contributor

guusdk commented Jan 5, 2024

When a project uses a JIRA filter to track issues that are up for grabs, the website should list the number of open issues (as it does for other trackers).

JIRA provides a REST API that can be used to collect the data. This can be used by supplying the filter identifier.

Given an up-for-grabs URL like this: https://igniterealtime.atlassian.net/issues/?filter=10004, take the filter ID (10004 in this example), and use it in a REST API call on the same site, like this: https://igniterealtime.atlassian.net/rest/api/2/search?jql=filter=10004

This will return a JSON result. One of the first few attributes returned is a 'total' count, that can be used on the up-for-grabs website:

{
   "expand":"schema,names",
   "startAt":0,
   "maxResults":50,
   "total":14,
   "issues": [
@krishchvn
Copy link

Hi. I'd like to work on it. Can you assign it to me?

@AKASHYADAVO
Copy link

Hi, I am interested in taking this issue on .

@yeebenja
Copy link

yeebenja commented Nov 6, 2024

Hello! I would like to be assigned this issue.

@guusdk
Copy link
Contributor Author

guusdk commented Nov 6, 2024

I'm not sure why people want to explicitly be assigned the issue. I'm sure that if you just create a pull request with the suggested changes, people would be happy to review it.

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

No branches or pull requests

4 participants