Status not showing in created queues?

[Deleted user]

Solution: As Jack below proposed, there was a custom field named "status" that was taking precedence when searching for status columns in the edit portion of the queues.  Deleting that custom field and adding back the status column to the queue pulled in the correct status field.

Question: Morning, I am in the process of transitioning our ServiceDesk over to Jira.  I have setup 2 queues for our ServiceDesk project and have edited the columns but the "Status" column is blank.  This column is showing that status labels on other standard queues like All open.  So is there something else I need to do to get the status labels to show up when creating queues?

Thanks!

Jason

[Jack Brickey · Accepted solution]

well that is rather odd. Let's recreate the queue w/in the Jira Search for issues method:

• edit the queue and copy the JQL that represents the queue
• navigate to Search issues and paste the JQL in
• include status in the columns

results?

[Deleted user]

Thank you for your response.  Currently the only JQL is: Escalation = "Tier 1 Service Desk".  I have a custom field called Escalation that has 5 options, only two are tied to queues that use the same basic syntax but both have the same issue with the status column.

When I ran the search it does show the 3 SER key requests from our ServiceDesk project and Status is included in the preview.  Just as it shows in the all open queue.  Is my syntax incorrect?  I would think it would not pull the requests if that was the case.

Jason

[Jack Brickey]

well this is just weird for sure. Your JQL is fine. You said you had five values for 5 queues. Are all queues showing blank status?

Can you verify that you don't have some custom field called "Status". Don't think that is even possible TBH but would edit the display to verify.

[Deleted user]

Nailed it!  There was in fact a custom field named "Status" that was not even being used.  Deleting that custom field removed it from my columns and then adding status back pulls in the correct status fields now.  Strange that we were able to even create a custom field with that name.

Thanks!

Jason

[Jack Brickey]

yikes. definitely don't want a custom field that uses a Jira default field name. :-)

If your question is now resolved be sure to click the checkmark above to accept solution as it helps others when they have a similar question.