Message8329
Hi John, you write:
> Hmm, I can't reproduce this with one of my trackers. It doesn't have a superseder field,
> but it does have another issue multilink. In my tracker I see:
>
> "Error: you may only enter ID values for property seealso"
looking at the code this only happens when the class in question does not have a key (i.e. getkey() returns None). It specifically doesn't catch the case where the class *does* have a key like the superseder property linking to user (where the key is the username).
To reproduce the problem you may try to enter a non-existing username into the 'Superseder' property of *this* tracker.
I've currently only set up a test framework with postgres backend, I'll try to test this with another backend, too... |
|
Date |
User |
Action |
Args |
2025-01-28 11:04:32 | schlatterbeck | set | messageid: <1738062272.85.0.208820844985.issue2551376@roundup-tracker.org> |
2025-01-28 11:04:32 | schlatterbeck | set | recipients:
+ schlatterbeck, rouilj |
2025-01-28 11:04:32 | schlatterbeck | link | issue2551376 messages |
2025-01-28 11:04:32 | schlatterbeck | create | |
|