Can HumDay connect to JIRA 7.6.1?

Yes. HumDay reads JIRA 7.6.1's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 324 operations are documented.

Do I need to write code to automate JIRA 7.6.1?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your JIRA 7.6.1 account.

What can HumDay do in JIRA 7.6.1?

171 of the 324 documented operations change something in JIRA 7.6.1, and 153 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my JIRA 7.6.1 account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to JIRA 7.6.1 is held behind that approval.

Automate JIRA 7.6.1

HumDay reads JIRA 7.6.1’s own published API description and derives 324 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate JIRA 7.6.1

What HumDay can do in JIRA 7.6.1

171 documented operations change something in JIRA 7.6.1. The 60 most useful are listed here.

POSTCreates issues or sub-tasks from a JSON representation./api/2/issue/bulk
POSTCreate user. By default created user will not be notified with email. If password field is not set then password will be randomly generated./api/2/user
POSTCreates an issue or a sub-task from a JSON representation./api/2/issue
POSTCreates a new session for a user in JIRA./auth/1/session
POSTCreates an issue link between two issues./api/2/issueLink
POSTCreates an issue type from a JSON representation and adds the issue newly created issue type to the default issue type scheme./api/2/issuetype
POSTCreate a new issue link type./api/2/issueLinkType
POSTSends a notification (email) to the list or recipients defined in the request./api/2/issue/{issueIdOrKey}/notify
POSTAdds a new comment to an issue./api/2/issue/{issueIdOrKey}/comment
POSTAdds a user to an issue's watcher list./api/2/issue/{issueIdOrKey}/watchers
POSTCreates a new ProjectRole to be available in JIRA./api/2/role
POSTCreates a new filter, and returns newly created filter./api/2/filter
POSTReturns a list of statements explaining why the password policy would disallow a proposed password for a new user./api/2/password/policy/createUser
POSTReturns a list of statements explaining why the password policy would disallow a proposed new password for a user with an existing password./api/2/password/policy/updateUser
POSTCreates a new project./api/2/project
POSTCreate a version via POST./api/2/version
POSTCreate a component via POST./api/2/component
POSTCreate a new workflow scheme./api/2/workflowscheme
POSTCreate a project category via POST./api/2/projectCategory
POSTAdds a new worklog entry to an issue./api/2/issue/{issueIdOrKey}/worklog
DELETERemoves a user from an issue's watcher list./api/2/issue/{issueIdOrKey}/watchers
POSTAdds given user to a group./api/2/group/user
POSTReindexes one or more individual issues./api/2/reindex/issue
POSTAdd user to given application./api/2/user/application
PUTSets the default share scope of the logged-in user./api/2/filter/defaultShareScope
POSTCreates temporary avatar using multipart./api/2/user/avatar/temporary
DELETERemoves user./api/2/user
PUTModify user. The "value" fields present will override the existing value. Fields skipped in request will not be changed./api/2/user
POSTCreates a custom field using a definition (object encapsulating custom field data)/api/2/field
POSTCreates a group by given group parameter Returns REST representation for the requested group./api/2/group
PUTModify currently logged user./api/2/myself
POSTPerforms a search using JQL./api/2/search
POSTRuns any pending delayed upgrade tasks./api/2/upgrade
DELETELogs the current user out of JIRA, destroying the existing session, if any./auth/1/session
DELETERemoves preference of the currently logged in user./api/2/mypreferences
PUTSets preference of the currently logged in user./api/2/mypreferences
PUTAssigns an issue to a user./api/2/issue/{issueIdOrKey}/assignee
POSTCreate a remote version link via POST./api/2/version/{versionId}/remotelink
POSTCreates or updates a remote issue link from a JSON representation./api/2/issue/{issueIdOrKey}/remotelink
POSTAdd one or more attachments to an issue./api/2/issue/{issueIdOrKey}/attachments
DELETERemoves given user from a group./api/2/group/user
POSTConverts temporary avatar into a real avatar/api/2/user/avatar
DELETEReset the default columns for the given user to the system default./api/2/user/columns
PUTSets the default columns for the given user./api/2/user/columns
POSTReturns worklogs for given worklog ids./api/2/worklog/list
PUTModify user password./api/2/user/password
PUTSets the default system columns for issue navigator./api/2/settings/columns
DELETERemove user from given application./api/2/user/application
PUTUpdates an existing filter, and returns its new value./api/2/filter/{id}
DELETEDeletes the specified issue type./api/2/issuetype/{id}
PUTUpdates the specified issue type from a JSON representation./api/2/issuetype/{id}
DELETERemove an attachment from an issue./api/2/attachment/{id}
DELETEDeletes an issue link with the specified id./api/2/issueLink/{linkId}
DELETEDelete an issue. If the issue has subtasks you must set the parameter deleteSubtasks=true to delete the issue. You cannot delete an issue without its subtasks also being deleted./api/2/issue/{issueIdOrKey}
PUTEdits an issue from a JSON representation./api/2/issue/{issueIdOrKey}
DELETEDeletes an existing comment./api/2/issue/{issueIdOrKey}/comment/{id}
PUTUpdates an existing comment using its JSON representation./api/2/issue/{issueIdOrKey}/comment/{id}
POSTAdds an actor (user or group) to a project role./api/2/project/{projectIdOrKey}/role/{id}
DELETEDeletes a group by given group parameter./api/2/group
DELETEDelete the specified issue link type./api/2/issueLinkType/{issueLinkTypeId}

What HumDay can read from JIRA 7.6.1

These are the operations a schedule or a trigger can watch.

GETReturns a list of users matching query with highlighting./api/2/user/picker
GETReturns a list of users that match the search string./api/2/user/search
GETReturns suggested issues which match the auto-completion query for the user which executes this request./api/2/issue/picker
GETReturns a list of active users that match the search string./api/2/user/viewissue/search
GETReturns a list of users that match the search string./api/2/user/assignable/search
GETReturns a list of all issue types visible to the user/api/2/issuetype
GETReturns a list of users that match the search string and can be assigned issues for all the given projects./api/2/user/assignable/multiProjectSearch
GETReturns a list of users and groups matching query with highlighting./api/2/groupuserpicker
GETSearches for issues using JQL./api/2/search
GETReturns a list of all issue priorities./api/2/priority
GETReturns a list of available issue link types, if issue linking is enabled./api/2/issueLinkType
GETReturns a paginated list of notification schemes./api/2/notificationscheme
GETReturns all comments for an issue./api/2/issue/{issueIdOrKey}/comment
GETGet a list of the transitions possible for this issue by the current user, along with fields that are required and their types./api/2/issue/{issueIdOrKey}/transitions
GETThis resource returns a paginated list of users who are members of the specified group and its subgroups./api/2/group/member
GETReturns auditing records filtered using provided parameters/api/2/auditing/record
GETReturns the meta data for creating issues./api/2/issue/createmeta
GETReturns the default share scope of the logged-in user./api/2/filter/defaultShareScope
GETReturns a user. This resource cannot be accessed anonymously./api/2/user
GETReturns a list of all fields, both System and Custom/api/2/field
GETReturns currently logged user./api/2/myself
GETReturns a list of all statuses/api/2/status
GETReturns all projects which are visible for the currently logged in user./api/2/project
GETReturns the result of the last upgrade task./api/2/upgrade
GETReturns information about the currently authenticated user's session./auth/1/session
GETReturns a list of all dashboards, optionally filtering them./api/2/dashboard
GETReturns a list of all resolutions./api/2/resolution
GETReturns all permissions in the system and whether the currently logged in user has them./api/2/mypermissions
GETReturns preference of the currently logged in user./api/2/mypreferences
GETReturns a list of all status categories/api/2/statuscategory
GETReturns all issue security schemes that are defined./api/2/issuesecurityschemes
GETReturns a list of all alternative issue types for the given issue type id./api/2/issuetype/{id}/alternatives
GETReturns an issue's subtask list/api/2/issue/{issueIdOrKey}/subtask
GETReturns the list of watchers for the issue with the given key./api/2/issue/{issueIdOrKey}/watchers
GETReturns all avatars which are visible for the currently logged in user./api/2/user/avatars
GETReturns the default columns for the given user./api/2/user/columns
GETReturns groups with substrings matching a given query./api/2/groups/picker
GETReturns the meta information for an attachments, specifically if they are enabled and the maximum upload size allowed./api/2/attachment/meta
GETReturns the list of requirements for the current password policy./api/2/password/policy
GETReturns the favourite filters of the logged-in user./api/2/filter/favourite

How automating JIRA 7.6.1 works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live JIRA 7.6.1 account.
Grant access, then go live. You approve the specific JIRA 7.6.1 operations it may use — and only those.