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

Illegal issue+activity combination #935

Open
kusalananda opened this issue Feb 2, 2024 · 0 comments
Open

Illegal issue+activity combination #935

kusalananda opened this issue Feb 2, 2024 · 0 comments
Labels
bug Something isn't working frontend This is likely affecting the frontend

Comments

@kusalananda
Copy link
Member

kusalananda commented Feb 2, 2024

Describe the bug

Several users have reported adding a Redmine issue with an activity to their Urdr interface, but that they subsequently have been prevented from logging time on the issue+activity combination.

Looking closer at what appears to happen when this issue occurs reveals that the activity that is added in the UI has a "parent" activity ID rather than an activity ID connected to the specific Redmine project in question.

In Redmine, activities are "enumerations", and there is a set of "parent" enumeration entries that are duplicated for each Redmine project. As an example, the "parent" enumeration ID for the "Implementation" activity is 14, but the "Implementation" activity that Redmine issue 6484 (connected to Redmine project 381, "Externally funded projects") may use has the ID 77.

It is therefore understandable that a user who tries to log time on the combination (6484,14) gets the error message, even though the "Implementation" activity (ID 77, not 14) should be allowed. The bug is that, in this example, ID 77 should have been given to the user when they added the issue to their Urdr UI, not ID 14.

I've tagged this with "frontend" only because I think that's the best place to start looking for the cause of the issue, since it manifests in the graphical interface. It may well end up being a bug in the backend somewhere.
Examples of this bug (the first link is the exact example used above):

Steps to reproduce

I have not been able to reproduce the error in the UI.

More information

Possibly related to #870

@kusalananda kusalananda added bug Something isn't working frontend This is likely affecting the frontend labels Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working frontend This is likely affecting the frontend
Projects
None yet
Development

No branches or pull requests

1 participant