Robert (Community Member) asked a question.

June 30, 2020 at 3:07 AM
I am unable to import any issues into Jira Cloud

I have managed to configure the integration for Jira Cloud, at least up to the point where almost everything seems to be correct, and from the "Selective Import" I can get a valid list of issues that I want to import.

 

However, no matter which issues I pick, or how many, it says it has imported the items, but they never seem to get created in Jira.

 

I am suspecting it might have something to do with Transition mapping (since it cannot be customized, it will almost always not match, and I know ours doesn't match exactly), but of course, there is no output, and the Troubleshooting page doesn't help troubleshoot anything, only reset the cache so you can try again.

 

Any suggestions on how to go about diagnosing this and getting it working?

  • 5 answers
  • 1.31K views

  • Jason M., Veracode Support (Veracode)

    Per our steps from our Engineering team, the resolution to configuring the settings to check when there are JIRA Cloud Import Issues:

    Once you configured your JIRA Cloud Plugin, but see the errors during any import or get a message that "All flaws are imported", but do not see any issues created in your JIRA Project, the reason may be that Veracode Custom Fields are not associated with Project Screens in the Jira Cloud. Please check the following:

     

    1. Navigate to the screens for the Project to where you configured to import your Veracode Findings (JIRA Administration--> Issues --> Screens)

    2. Locate the Screen for the Issue type you configured your Findings to Import as, make sure this screen has 3 required custom fields added: "Veracode Link", "Environment", and "Mitigation Status and Comments"

    3. If there is a separate Default Screen in the same Project, make sure that same 3 Custom fields are added as well.

     

    If all or any of 3 Custom Fields are not added to the appropriate screens, manually add them by selecting the fields from the drop-down box on the Screen.

     

    Please see our help Center for further Instructions on "Associating Veracode Fields with Project Screens in Jira Cloud"

    https://help.veracode.com/reader/4ULk2mjyYUeYb8xd_2nDVw/H_0jRVcnkppxHuOuR2b2WQ (#11)

     

    Note: After each configuration change, please clear the Plugin's Cache by navigating to Troubleshooting --> Clear Cache in the Veracode Plugin Menu.

     

    Jason

    Community Support Engineer

    Expand Post
    Selected as Best

  • Jason M., Veracode Support (Veracode)

    Hello @Robert (Community Member)​ ,

     

    To ensure that there are no issues with importing items into JIRA, the CSV file requires the issue field name exactly as it appears in JIRA with no white space on either end of the column. The importer looks for an exact match of the column name and the name on the JIRA create or edit screen.

     

    In regards to the transition mapping, please look over this related article in our Help Center to help the transfer from the Veracode fields to the JIRA Cloud fields: https://help.veracode.com/reader/zriMYydma5AUKAFYh3xDnw/jjk6WnhmofPoGC8eRQw6bw

     

    Jason

    Community Support Engineer

    Expand Post

    • Robert (Community Member)

      I presume you mean under the covers it generates a CSV file that it tries to import into Jira (as I don't see a CSV file as part of the process at all).

       

      I'm also not mapping any fields (largely because I cannot map anything useful, or "unmap" anything I want to unmap -- like "Found in version").

       

      I'm not sure why it would match things on the edit or create screens -- it should be filling in fields via the internal APIs for plug-ins, however, even so, it should at least either say "failed to import entries" when it actually doesn't import the entries instead of "All entries imported".

       

      Also, it should indicate what the problem is -- since this is a "cloud instance", there is no way for me to get at the Jira Java logs, or turn up logging levels.

       

      Any further suggestions?

      Expand Post

      • Irina R., Veracode Support (Veracode, Inc.)

        Hello @Robert (Community Member)​ 

         

        Please send an email to support@veracode.com with title JIRA Cloud Integration

        We need some more information, may need to set up a call to troubleshoot.

         

        Thank you!

        Irina Rozina - Integrations Engineer

         

        Expand Post

      • Jason M., Veracode Support (Veracode)

        Per our steps from our Engineering team, the resolution to configuring the settings to check when there are JIRA Cloud Import Issues:

        Once you configured your JIRA Cloud Plugin, but see the errors during any import or get a message that "All flaws are imported", but do not see any issues created in your JIRA Project, the reason may be that Veracode Custom Fields are not associated with Project Screens in the Jira Cloud. Please check the following:

         

        1. Navigate to the screens for the Project to where you configured to import your Veracode Findings (JIRA Administration--> Issues --> Screens)

        2. Locate the Screen for the Issue type you configured your Findings to Import as, make sure this screen has 3 required custom fields added: "Veracode Link", "Environment", and "Mitigation Status and Comments"

        3. If there is a separate Default Screen in the same Project, make sure that same 3 Custom fields are added as well.

         

        If all or any of 3 Custom Fields are not added to the appropriate screens, manually add them by selecting the fields from the drop-down box on the Screen.

         

        Please see our help Center for further Instructions on "Associating Veracode Fields with Project Screens in Jira Cloud"

        https://help.veracode.com/reader/4ULk2mjyYUeYb8xd_2nDVw/H_0jRVcnkppxHuOuR2b2WQ (#11)

         

        Note: After each configuration change, please clear the Plugin's Cache by navigating to Troubleshooting --> Clear Cache in the Veracode Plugin Menu.

         

        Jason

        Community Support Engineer

        Expand Post
        Selected as Best

  • Robert (Community Member)

    Just as a follow up to this thread. I did eventually get things working by making sure that all my screens, etc. had all the Jira fields on them. It was a bit painful, and some of our screens now have more information than needed, but at least it's functioning (albeit with lots of bugs and issues and limitations -- separate posts made about obvious bugs).

Topics (2)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.