Fix priority property from redmine issues

GothenburgBitFactory / bugwarrior

Pull github, bitbucket, and trac issues into taskwarrior

http://pypi.python.org/pypi/bugwarrior

GNU General Public License v3.0

732 stars 209 forks source link

Fix priority property from redmine issues #889

Closed hlobit closed 2 years ago

hlobit commented 2 years ago

Priorities could not be pulled from a redmine server until I lowercased the name property. I then changed to a non-default priority in tests to ensure the result is as expected.

ryneeverett commented 2 years ago

I'm not a redmine user myself. Care to test this out @CaptainQuirk?

CaptainQuirk commented 2 years ago

The fix definitively makes sense but unfortunately, I seem to hit several blocks here :

My redmine instance is in French, so the PRIORITY_MAP will not work as is
If I change the mapping just to test it out, although debugging shows me that the proper taskwarrior priority is guessed from the redmine priority, the task priority remains incorrect

hlobit commented 2 years ago

Hi @CaptainQuirk,

yes ideally this should not rely on priority names or priority map should be configurable
priority is by default a static field (I guess in most use cases the users want to manage it independently in taskwarrior)

With this config in .config/bugwarrior/bugwarriorrc I got it imported:

[general]
static_fields =