Jira

Jira runs the planning at companies large enough to have a formal one, which in property management usually means an internal development team, a systems function, or a group with a project office.

Its cost is friction. Raising a well-formed ticket takes long enough that small things go unreported, which is how a known annoyance survives for a year without anyone ever writing it down.

Connecting Jira lowers that cost to a sentence. A ticket can be raised as the problem is described, with the right project and type, and sprint status answered without opening a board. The board keeps its structure; what changes is how much effort stands between noticing something and recording it.

One caution: resist the temptation to run property maintenance through Jira because it is already there. Guest-driven work needs to reach cleaners and contractors who will never log into an issue tracker, which is what ProhostAI tasks are for.

Once Jira is connected, ProhostAI works with your issues and sprints in plain language.

Read

• Check sprint status See what is in progress, blocked or due. "What is still open in the current sprint?"
• Find issues Locate tickets by project, assignee or subject.

Create & update

• Create issues Raise a well-formed ticket in the right project as the problem is described.
• Update and transition Move tickets through your workflow and add comments.

Jira connects through Atlassian OAuth, so ProhostAI never sees your password.

1. Open ProhostAI and go to Settings → Connections.
2. Search for Jira and select Connect.
3. Sign in to Jira and approve the permissions.
4. Ask what is open in the current sprint to confirm it works.

• Access follows the connected Atlassian account’s project permissions.
• Your workflows, issue types and custom fields are used as they are.
• This is for internal projects; guest-driven maintenance is usually better in ProhostAI tasks where your operations team works.