![]() According to the Atlassian community, do not store more than 200,000 issues on a single JIRA instance.rag-and-Drop issue prioritization feature is available in Jira but not in Bugzilla. To prevent your users from changing the Mitigation Status and Comments field, Veracode recommends that you make the field read-only. In Jira, you can easily drag and drop the issues based on the priority of the issues, but this will not be possible in Bugzilla. The custom fields appear on the Configure Screen page. At this point, we have all the tools and the data we need to tranform JIRA issues into Bugzilla bugs. To handle these changes, I map JIRA strings to Bugzilla strings in my main script. In my case, they did already exist, but the names had been changed. From the Field name dropdown menu, select Mitigation Status and Comments and click Add. Otherwise, Bugzilla will use the default product and component.From the Field name dropdown menu, select Veracode Link and click Add.Click Configure to display the Configure Screen page for the selected template.Automating the processes was critical beyond the. ![]()
0 Comments
Leave a Reply. |