Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to Display the Jira Issue Macro without the Summary

Matthias Pfeilsticker
December 4, 2019

If we Crate a Jira Issue from Confluence this Issue is displayed without the Summary. Just the Key and the Status. Great.

 

If we add a Single Jira Issue with the Jira Issue Macro the Issue is Displayed with Key,Summary and Status. But we don't want the Summary there.

 

On the Help Page (https://confluence.atlassian.com/doc/jira-issues-macro-139380.html) we found this :

You can choose to show just the issue key, or the issue key and a summary. Select the macro placeholder and choose Show Summary or Hide Summary.

 

But we are not able to select the issue in a way we get able to choose this.

 

How we do it?

3 answers

1 accepted

2 votes
Answer accepted
Jeremy Largman
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 12, 2011

It sounds like you have an encoding problem. Check Troubleshooting Character Encodings. Often it's the database - that's the most likely.

0 votes
Jeffrey Harris
August 22, 2011

In my case, Jeremy is exactly correct.

When we installed Confluence, somehow the database was set to "Latin-1" character encoding. Not good for displaying double-byte characters. Once we changed the database encoding to UTF-8, and confirmed that both the App Server and Confluence application were also set to UTF-8, then things started working famously.

I haven't had any trouble with Japanese character display since.

David Dube
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 23, 2011

Did you just follow this procedure, or is there an easier way?

Did you lose any content? Of the content that was already saved (using Japanese characters)... was the content retained or did you have to re-copy/add the content?

Dave

Jeffrey Harris
August 23, 2011

We followed that procedure. Resetting the database encoding was a bit of a pain, but it was necessary to get things working.

0 votes
David Dube
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 22, 2011

Hi Timplooker,

I'm having the same issue... were you able to resolve this on your end? I was able to find a language pack, but it's reportedly only compatible with v3.2 - v3.2.1, and I'm running with 3.4.1.

Dave

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events