Jira issues macro prints poorly (See screenshot) if using custom fields that are quite long.

      The Iframe mechanism is great for displaying JiraIssues in Confluence page. If the Jiraissues columns are too long to be displayed in the page, the Iframe mechanism will produce a scroll bar.

      However, when printing the page the fields will be cut (see screenshot).

      Need a better mechanism to handle this.

      Jiraissues macro to test with:

      {jiraissues:anonymous=true|url=http://jira.atlassian.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?query=jiraissues+AND+empty&summary=true&description=true&body=true&pid=10470&tempMax=10|columns=Key;Company;Pr;Summary;Status;Updated;Reporter;Assignee;Res;Created;Description;Since last reply;Last commented by user?}
      

        1. Picture 3.png
          267 kB
          Roy Hartono [Atlassian]
        2. Printing+Firefox3+Mac.png
          111 kB
          Justin Sinclair
        3. Printing+Safari4+Mac.png
          141 kB
          Justin Sinclair

            [CONFSERVER-15985] jiraissues macro prints poorly

            TruongA added a comment - - edited

            It is no longer an issue in JIRA macro 5.1 bundle with Confluence 5.3 . Dynamic mode is deprecated when we consolidated the existing two macros into a single macro with one interface and added additional features.

            TruongA added a comment - - edited It is no longer an issue in JIRA macro 5.1 bundle with Confluence 5.3 . Dynamic mode is deprecated when we consolidated the existing two macros into a single macro with one interface and added additional features.

            also broken in Confluence 3.0

            Roy Hartono [Atlassian] added a comment - also broken in Confluence 3.0

              Unassigned Unassigned
              rhartono Roy Hartono [Atlassian]
              Affected customers:
              4 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: