BUG REPORT: Agile Phase Created with Type “[Object object]” in Project Workspace

jordimsant
Kilo Sage

Hi Community,

 

I would like to report what seems to be a bug in Project Workspace when working with Agile-type projects.

 

Issue Description

In a project configured as Agile, when a user creates a new Agile Phase and presses Enter, the system automatically allows the creation of another phase inline — without clicking the “Create Agile Phase” button again.

From a UX perspective, this behavior is actually convenient and does not seem problematic by itself.

However, the issue is that:

  • The newly auto-created phase is not assigned the type “Agile”.

  • Instead, its type is displayed as [Object object].

 

Expected Behavior

When creating Agile phases inline (after pressing Enter):

  • The new record should automatically inherit or default to the Agile phase type.

  • The phase type field should correctly display “Agile”, not [Object object].

 

Actual Behavior

  • The first phase is created correctly.

  • Pressing Enter enables inline creation of another phase.

  • The new phase is created with its type showing as [Object object] instead of “Agile”.

 

Environment

  • Instance type: Personal Developer Instance (PDI)

  • Workspace: Project Workspace

  • Project type: Agile

 

Additional Observations

The behavior itself (pressing Enter to quickly create another record) seems intentional and useful. The issue appears specifically related to:

  • Improper handling of the phase type value during inline creation.

  • Possible incorrect object-to-string conversion in the UI layer.

It looks like a front-end issue rather than a configuration problem.


Where Should This Be Reported?

Since this was found in a Personal Developer Instance (PDI), I do not have access to official ServiceNow Support to open a HI case. Does anybody know where I should address?

 

If anyone else can reproduce this issue — especially in non-PDI environments — it would be helpful to confirm whether this is a broader product defect.

 

Thanks in advance for any insights.

0 REPLIES 0