Open to wacky suggestions!
I want an HTML table to display, not as HTML but as the actual table. I am aware that this can be done on pages on which the user has the capacity to enter data into fields, such as on the "Edit this issue" page, (by entering the HTML into a field's description), but I need it to display in the JIRA itself.
I am using JIRA version 3.13.4, and upgrading to a later version is unfortunately not an option.
Thanks!
I don't understand where this table should go? "In the JIRA itself" contradicts "the user has the capacity to enter data into fields"
Seriously though, upgrade.
It isn't a contradiction. When a user clicks into the JIRA to view it they have the capacity to enter comments... they do not have the capacity to add or modify the values stored in fields. They gain that capacity when they move onto a different page.
This matters because each field has a description, which displays if the user can add or modify the values stored in fields, such as when on the "Edit this issue" page. If I add HTML to the description, it will render on the page. But if the user is simply viewing the JIRA, the descriptions are not present, therefore neither is the HTML.
I was deliberately vague about the location of the HTML table, because I'll take any suggestion at this point, whether it's displaying it within a field, or a comment, or elsewhere on the page.
Believe me, upgrading really, really isn't possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This still doesn't answer the question. Where do you want this table to go? Let me ask this differently. Is this table issue data, or is it static non-issue data?
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.
Does the data in your table belong to the issue being displayed? Like the fields ("in the JIRA")? Or is it a static block of stuff that you want to display on the view screen (i.e. not in the JIRA)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The table will contain hard-coded data. It does not need to be dependent on the values within fields, or the workflow, or anything else.
I suppose the ideal location would be for it to be positioned at the top of the JIRA where the custom fields are located. This area as far as I know doesn't have a name, it just displays at the top of every JIRA, and contains the custom fields and their values.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, you've got two options
I say that because the JIRA Toolkit does exactly what you describe with putting it in the "area where custom fields are located". Have a look at the old versions for it and find the highest that works for 3.13 and install it. Then go to "add custom field" and look for "message field for view". Add one of them, stick it on the view screen and you'll be able to put html into the default value for it, which will then render a table on issue view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sounds ideal. Unfortunately the download link for the version I would need is broken, and I can't find it anywhere else, but I've emailed Atlassian to ask if they can fix it:
https://marketplace.atlassian.com/plugins/com.atlassian.jira.toolkit/versions
Thanks very much for your help, and for persevering through the explanation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.