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.

Sign up for GitHub

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

Jump to bottom

Using with redmine isn't setting closed status correctly since at least python-redmine 1.5 #19

Open
PatSunter opened this issue Feb 1, 2018 · 0 comments
Open

Using with redmine isn't setting closed status correctly since at least python-redmine 1.5 #19

PatSunter opened this issue Feb 1, 2018 · 0 comments

Comments

@PatSunter
Copy link

In my use with redmine, I have python-redmine 1.5.1 installed, and I found that the issue status (whether closed or not) isn't being set correctly. So, in your final Sphinx document the issues create valid links but don't get a strike-through them if they are closed as is supposed to happen.

It appears the relevant code just checks if the issue.status is 'Closed', but the Python redmine API has been modified/upgraded at some stage to not use a string for status but instead a class as part of their relational system: https://python-redmine.com/resources/issue_status.html
PatSunter added a commit to PatSunter/sphinxcontrib-issuetracker that referenced this issue Feb 1, 2018
@PatSunter
[Fix ignatenkobrain#19] redmine resolver to get closed status.
dda7f32 
Tested using python-redmine v1.5 but consistent with
latest python-redmine docs, see
https://python-redmine.com/resources/issue_status.html.

issue status in python-redmine isn't a string it's now
a class, but calling str() on it makes it
backwards-compatible with prev.  approach.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PatSunter