I have my data in Sharepoint excel ..
inaddition to the Ticket number, summary, desc, there are custom fields(columns) of checklist questions like ..
Is this having Solaris
Has the DB request raised
Is this under complex category
etc ..
These are not just 'Yes or No' answers .. sometimes the answers can be Text as well
Now, trying to bring all these Sharepoint records as JIRA Tickets ..
While i can achieve it by having these columns as a Smart Checklist in JIRA, the challenge is that im not able to bring this as a display in JQL(Cloud) ..
i can render the Checklist through my JQL(list view .. selecting the columns to be displayed) but it just displays all the Checklists in one cell which is not read friendly or UI friendly ..
in other words, is it possible to display each of my checklist queries in different columns in JQL output !!
Please help.
Hello @Ramu
No, that is not possible.
The entire checklist is stored in a single custom field. The JQL list view is designed to display a field as a column. There is no capacity for displaying a portion of a field as a column.
A work around would be to create separate custom fields for the checklist items that you want to see as separate columns.
Another option would be to explore other third party apps that provide more customizable views of search results.
Ok .. Thanks @Trudy Claspill .. when you say 'A work around of creating separate custom fields .. !' .. i dint get it ..
in a JIRA Ticket, there is only one section to add the checklist items right .. may be im overlooking your response .. please let me know
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You would create entirely separate custom fields; one for each checklist item. You would implement a solution to update those custom fields from the information available in the Smart Checklist. Those custom fields could then be displayed as columns in the list view of JQL results.
The exact method to create the separate custom fields depends on the type of project/space where the Checklist is implemented.
https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-custom-fields/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ramu
Trudy is right - displaying individual checklist items as separate columns in JQL list view isn't something native Jira (or any app) can do, since it's a platform-level limitation.
That said, I'm from the Table Grid Next Generation team and wanted to suggest a slightly different approach that might solve the underlying need.
Instead of using Smart Checklist and then trying to report on it, you could model the same data as a Table Grid - where each of your checklist questions (Is this having Solaris, Has the DB request raised, Is this under complex category, etc.) becomes its own column inside the grid, accepting both Yes/No and free-text answers via String/Textarea columns.
This gives you a few things Smart Checklist can't:
Readable structured view on the issue - each question is clearly separated in its own column, not dumped into a single cell.
JQL search by grid content - with Index data enabled on a column, you can search issues using issue in grids("Grid Name", "Column Name ~ value") to find issues matching specific checklist answers across your project.
Push grid values into native Jira custom fields via REST API + Automation - if you need each checklist answer to be searchable as a standard Jira custom field in JQL (e.g. "Is this having Solaris" = Yes), you can use Table Grid's REST API together with a Jira Automation rule to automatically read the grid column value and write it into a dedicated Jira custom field. This way each question gets its own searchable field and own column in JQL search - no manual sync needed.
Export to Excel/CSV - the full grid data exports cleanly with each question in its own column, much closer to your original SharePoint format.
It's a different mental model from checklist → report, but it keeps the data structured from the start rather than trying to parse it after the fact.
Feel free to try it on the Atlassian Marketplace Table Grid Next Generation - and don't hesitate to reach out at support@tablegrid.atlassian.net or Table Grid Support Portal
if you'd like help setting it up!
Regards,
Duong Nguyen Hong
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great @Duong Nguyen Hong ..
Automation .. yes .. but REST API .. its something i need to explore (will try) ..
looks interesting .. let me try and Table Grid (hope it is supported in my Org restricted Cloud Confluence ..
Thanks again ..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.