Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-13887

Syntax error when mapping multi-line text field from JIRA to Perforce

    XMLWordPrintable

Details

    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 3 November 2017

      Hi everyone,

      The issue has not get additional interest since the time it has been reported. Additionally it lacks important information as an affected version, etc.

      Therefore I'm resolving the issue as Timed Out.

      Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

      Cheers,
      Ignat Alexeyenko
      Jira bugmaster.

      Show
      Atlassian Update – 3 November 2017 Hi everyone, The issue has not get additional interest since the time it has been reported. Additionally it lacks important information as an affected version, etc. Therefore I'm resolving the issue as Timed Out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

    Description

      Steps to reproduce

      1. enable Perforce Job Integration in JIRA
      2. create a multi-line text field in JIRA
      3. create a Job Checkbox custom field (in JIRA) for Perforce
      4. put these fields on Create Issue screen
      5. follow this to add a new field to Perforce jobs
      6. edit Perforce Job Integration -> Map Custom Fields and map the multi-line text field (step 2) to the Perforce field (step 5)
      7. create a new JIRA issue and tick Yes at the Job Checkbox field (step 3) to have it duplicated as a Perforce job
      8. also enter several lines into the multi-line text field e.g.:
        FirstLine
        SecondLine
        ThirdLine
        
      9. click Create

      Expected behavior

      The JIRA issue is duplicated as a Perforce job with the correct field mappings

      Actual behavior

      A Perforce job is not created because of this error in JIRA log:

      2015-03-12 21:58:29,401 http-bio-2768-exec-18 ERROR admin 1318x2636x1 jku0d9 192.168.1.100,0:0:0:0:0:0:0:1 /secure/QuickCreateIssue.jspa [com.perforce.api.Debug] P4 exited with an Error!
      2015-03-12 21:58:29,402 http-bio-2768-exec-18 ERROR admin 1318x2636x1 jku0d9 192.168.1.100,0:0:0:0:0:0:0:1 /secure/QuickCreateIssue.jspa [jirafisheyeplugin.perforce.listener.JobUpdateListener] Could not commit job: Job: DEMO-17
      User: admin
      Description:
      	Test
      
      com.perforce.api.CommitException
      	at com.perforce.api.Job.commit(Job.java:365)
      	at com.atlassian.jirafisheyeplugin.perforce.listener.JobUpdateListener.createJob(JobUpdateListener.java:42)
      	at com.atlassian.jirafisheyeplugin.perforce.listener.JobUpdateListener.workflowEvent(JobUpdateListener.java:30)
      ...
      Caused by: java.io.IOException: error: Error in job specification.error: Error detected at line 11.error: Syntax error in 'SecondLine'.
      	at com.perforce.api.P4Process.closeProcess(P4Process.java:587)
      	at com.perforce.api.Job.commit(Job.java:361)
      	... 226 more
      

      Note

      • If only 1 line is entered into the text field, a Perforce job is created successfully
      • In Perforce, multiple lines can be manually entered into the same field
      • It doesn't matter whether the multi-line text field in JIRA uses Default Text or Wiki Style renderer

      Workaround

      Using HTML tag <br/> to indicate new lines works. For example, using this single line in the multi-line text field:

      FirstLine<br/>SecondLine<br/>ThirdLine
      • It appears as a single line, thus it works
      • In Perforce, the field is rendered correctly with separate lines

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: