Jira Issue Key gets truncated on Scrum Board

[Manmohan Anand]

Hi,

If we fill all the field like priority, story points, Assignee etc. then on the card layout the JIRA issue-key is truncated on the scrum board and it makes difficult to drive the stand up as we can not refer to tickets using their unique issue key.

As you can see in the attached screenshot, the first 2 task's issue key is truncated if we add the story point, but for the 3rd task the issue key is not truncated when there is no story point.

Any solution for this?

[Manmohan Anand · Accepted solution]

This seems to be fixed now by its own. My column count is still the same.

[Bill Sheboy]

Hi @Manmohan Anand 

This is a known defect, and here is an example issue for it that you can watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-23833

Suggested work-arounds are to remove some card fields, disable some features, change the browsers zoom, etc.

Kind regards,
Bill

[Dave Mathijs]

@Manmohan Anand This means that you have too many columns on your board (simplifly!) or that the project key is too long.

[Manmohan Anand]

I have 10 columns which are essential to track the status of the tickets:

1. Blocked

2. To Do

3. In progress

4. In code review

5. Ready for QA

6. QA in progress

7. QA verified

8. Staging

9. Production

10. Done

The project key is XX-001