Need SubTask Relevant QueryString parameters

[LPK]

Hi Team,
Please help me here.

As part of daily routines of creating Tasks & their Sub-Tasks.

We generally create Sub-Task on Task page but I am planning for a below minor web based tool with single form.

I want to design a form with the following fields for a sub-task creation. The form can be built using any framework like Java, Dot Net or Appian BPM tool.

1. Task Number (Input field)

2. Assignee (Input Name/User ID/Email ID field)

3. Title for Sub Task (Input Field)

4. Description for Sub Task (Input Text Area field)

5. Due Date for Sub Task (Input Date Field)

6. SUBMIT button.

Expectation in Submit button:

The Submit button event will take the inputs of the above controls and appends the values to the respective parameters in the query string. 

Example: jiratickets.com/projectname/CreateSubTaskIssue!default.jspa?parentIssueId=123456&taskNumber=1234&assignee=ABCD&Title=xyz&description=uvwxyz&dueDate=01012020/

So, in my case, I would like to know the jira standard notations of the parameter names for the fields 1 to 5 above. Although Description can be omitted if not feasible.

Any suggestion please?

[Nic Brough -Adaptavist-]

You need to stop using the jira-users group to allow access to projects (except where a project genuinely is "access for everyone")

First, check the permission scheme lets you do what you want - e.g. "everyone in the role of R&D can read the project" and "Everyone in the role of tester can be assigned issues", and so-on

Then remove the jira-users group from the roles.  Replace it with other groups that accurately reflect what your users actually need, and/or put the users in the roles individually.

One general piece of advice - despite the defaults in a new off-the-shelf JIRA being set up this way, using the group jira-users for anything is a pain, and you should NOT do it.  Use Jira-users to say "can log in", and nothing else (other than genuinely global stuff - the "support this jira" project, "browse users", and "bulk edit" maybe).