direct issue creation and invalid data in database

Question

Hi All,

I am trying to use the direct issue creation feature as discribed below

https://confluence.atlassian.com/display/JIRA052/Creating+Issues+via+direct+HTML+links

we have a sepate page that auto complete the form and submit to jira via POST method to CreateIssueDetails!init.jspa

some jira projects we have are complex and it is possible that the form may not be complete. That is

1. required fields may not be filled

2. fields that accept only accept "YES" and "NO" might be filled with some thing else

when this thing happens the form will come with a warning that some required fields are not field or some other fields have invalid data. This is fine, the second step for the user is to complete the missing part and submit the form. so far so good.

But before the user corrected the form and hit submit. The server has already pre-processed the request and created initial entry in the database (like id, reporter, summary...). Lets say if the user did not do the second step, then we are left with inconcistent data in our database.

My expectation is that the server would reject any incomplete request and do not initiate entry creation until the form is complete. May be this is a configuration issue or something else. Is there something we can do to avoid this.

lomitec · Answer

Thanks Nic and Sumit for your quick response. This gives me enough direction to proceed.

Nic Brough -Adaptavist- · Answer

It also sounds like something else is creating bad issues then.

The validation DOES matter, because it should be stopping that, and if you're usign Jira without any dodgy hacks, it WILL stop broken issues being created.

I think it's time to step back and look at the whole system, because those POST calls in themselves are not causing the issue.

Sumit Kumar_fcyt6m · Answer

My issue and Bin's issue are on different instance and I was not even knowing him before this question came.

Actually it should not matter how you are doing the validation .. jira ideally should not allow issues on jiraissue table with null PKEY...because there in no importance of such issues when it comes to end users perspective since they won't be available at all to them.

The question "Why they got generated ?" I really didn't got much time to investigate the issue beacuse , I removed them from DB and now trying to write a trigger which can inform me whenever any such entry is made in Data Base.

I am pretty new to JIRA and there can be a lots of things which I might not be knowing so probably I am missing someting somewhere.

Thanks,

Sumit