[PUBTSKCONF-4] Missing requestor throws null pointer Created: 06/Jan/22  Updated: 26/Apr/23  Resolved: 26/Apr/23

Status: Closed
Project: Publication Task Configuration
Component/s: None
Affects Version/s: 6.1.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Chris Jennings Assignee: Richard Gange
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.75h
Original Estimate: Not Specified

Issue Links:
dependency
depends upon PUBTSKCONF-3 auto-approve as a subgroup is not wor... Closed
supersession
is superseded by PUBTSKCONF-5 Revert logic introduced by PUBTSKCONF-2 Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

For tasks that are missing a requestor field the AutoApprovableHumanTaskWorkItemHandler throws a null pointer at line 91.

Check for missing requestor and warn.



 Comments   
Comment by Richard Gange [ 26/Apr/23 ]

Closing as won't do because the logic of the code should be rewritten to not rely on the requestor. A follow up ticket will be created.

Generated at Mon Feb 12 10:32:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.