https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35657

--- Comment #76 from Marcel de Rooy <m.de.r...@rijksmuseum.nl> ---
 WARN   t/db_dependent/api/v1/ticket_updates.t
   WARN   tidiness
                The file is less tidy than before (bad/messy lines before: 58,
now: 80)

 WARN   t/db_dependent/api/v1/tickets.t
   WARN   tidiness
                The file is less tidy than before (bad/messy lines before: 65,
now: 70)

Status is updated on cataloguing/concerns.pl, but not on detail page ?
I cannot add an assignee without changing the status ?
I resolved a concern and wanted to revert its status again. Ending up in ticket
status RESO02 but update has ST01 again. See tables below.

I wont block this patch set as part of this tree. But still feel that the
functionality is not clear and the forms are not completely bug free.
Add experimental status?

MariaDB [koha_myclone]> select * from tickets;
+----+---------+-------------+---------------------+--------+---------------------+--------+-------------+-------------+---------------------+-----------+
| id | source  | reporter_id | reported_date       | title  | body             
  | status | assignee_id | resolver_id | resolved_date       | biblio_id |
+----+---------+-------------+---------------------+--------+---------------------+--------+-------------+-------------+---------------------+-----------+
| 34 | catalog |          51 | 2024-04-26 06:51:06 | test   | This is my
concern. | ST01   |          30 |          51 | 2024-04-30 13:29:57 |         1
|
| 35 | catalog |          51 | 2024-04-26 06:52:50 | Second | Test             
  | RESO2  |        NULL |          51 | 2024-04-26 07:14:14 |         1 |
+----+---------+-------------+---------------------+--------+---------------------+--------+-------------+-------------+---------------------+-----------+
MariaDB [koha_myclone]> select * from ticket_updates;
+----+-----------+---------+-------------+--------+---------------------+----------+--------+
| id | ticket_id | user_id | assignee_id | public | date                |
message  | status |
+----+-----------+---------+-------------+--------+---------------------+----------+--------+
| 13 |        34 |      51 |        NULL |      0 | 2024-04-26 06:53:04 |
Update 1 | NULL   |
| 14 |        34 |      51 |        NULL |      0 | 2024-04-26 06:54:36 |      
   | ST01   |
| 22 |        35 |      51 |        NULL |      0 | 2024-04-26 07:14:14 |      
   | RESO2  |
| 32 |        34 |      51 |          19 |      0 | 2024-04-30 13:24:34 |      
   | ST01   |
| 33 |        34 |      51 |          30 |      0 | 2024-04-30 13:29:27 |      
   | ST01   |
| 34 |        34 |      51 |        NULL |      0 | 2024-04-30 13:29:57 |      
   | RESO2  |
| 35 |        34 |      51 |          30 |      0 | 2024-04-30 13:30:09 |      
   | ST01   |
+----+-----------+---------+-------------+--------+---------------------+----------+--------+

Passed QA

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to