Is there a way to pass the JIRA task number to the macro after linking the page with it?

Question

JIRA

Hello everyone. Okay. Here I'm trying to organize a production process for HR using Confluence and JIRA. Some requirements have me stumped trying to optimize the process. That's why I'll ask.
How the department sees it:
- Jobs and Candidates are maintained in JIRA
- CV Database and Resume are maintained in Confluence
How to:
- HR creates a CV in Confluence from a custom blueprint template
- HR creates a JIRA sub-task under the Jobs task
- HR associates the CV page with sub-task.
- Technical experts, interviewers and hrs work with the Subtask (Interview, resume, offer, drop, etc.)
Need:
- Synchronize (or come up with some kind of facilitating mechanism) the state of the sub-task with the confluence page, or simply display the state of the task automatically.
What's the catch:
The problem is double work for HR. He needs to track the status of the application in JIRA, and then duplicate this in the CV in confluence.
There is a JIRA issue macro, but it won't do it automatically. With large volumes, it is problematic to update it every time, substituting the necessary tasks.
When linking the confluence page to JIRA, nothing is automatically pulled up. Maybe someone knows if there is a way to pass the state of the JIRA task to the macro after linking the page with it?

Answer 1

It seems to me that I understand what you want to do, but I do not understand what the problem is.
Jira issue macro https://confluence.atlassian.com/doc/jira-issues-m... was created just for this, in order to show the status of tasks in Confluence, you can use both individual links and large lists using JQL. These links will be updated each time the page is loaded.
I will try to describe the workflow:
* first, a task is created with a brief description of the vacancy
* then a page is created in Confluence, where the jira task is indicated at the very beginning (as far as I remember, this leads to linking the page with the task, I can’t check it now) with a detailed description
* then sub tasks are created
* pages are created for them with a CV on which the jira macro is also used
* on the main page of the CV description, you can display the entire list of subtasks for this vacancy.
Thus, for each CV there is a description and status in jira, there is a general page with all the necessary information.