How to make workflow validator checking on inactive assignee?

[Idiyana]

Currently, in my workflow, i used field required validator to check on empty assignee field. Besides just checking on the empty value, is there any way we can check if the assignee of an issue is inactive user during workflow transition?

[Lance]

Creating a workflow validator to check for inactive assignees in a system like Discord would depend on the specific features and capabilities of the platform. Here's a general approach you might take:

Understand Requirements: Clearly define what it means for an assignee to be "inactive." This could involve factors such as the last time they logged in, their participation in recent discussions, or any other relevant criteria.

Access API or Developer Tools: If Discord provides an API or developer tools, familiarize yourself with them. These tools often allow you to interact with the platform programmatically, enabling you to retrieve information about users and their activity.

Develop Script or Bot: Write a script or bot using the Discord API or developer tools to periodically check the activity status of assignees. This script should identify users who meet your criteria for being inactive. Liteblue

Implement Workflow Validator: Depending on the specific workflow management system you're using with Discord, implement a validator that integrates with your script or bot. This validator should trigger when assigning tasks or responsibilities and check whether the chosen assignee is inactive according to your criteria.

Feedback and Notifications: Decide what action should be taken if an inactive assignee is detected. This could involve providing feedback to the user attempting to assign the task, notifying project managers, or taking automated actions within the system.

Testing and Refinement: Test your workflow validator in a controlled environment to ensure it behaves as expected. Make adjustments as needed based on feedback and real-world usage.

Deployment: Once you're confident in your workflow validator, deploy it in your Discord server or workflow management system. Monitor its performance and make further refinements as necessary.

[Walter Buggenhout]

Hi @Lance,

Can you please not use ChatGPT to answer questions? Your answer does not have anything to do with the user's question and is not even closely related to Jira. Great that you want to help people out, but please do so from your own expertise and with information that is accurate and relevant to the matter. Thx. 

[Walter Buggenhout]

Hi @Idiyana,

Not as far as I know. But unless you are working in a massive organisation where people don't know the people they assign work to, I would hope it is very rare that an issue gets assigned to someone who is no longer working with you.

Jira (at least in company managed project) has a permission called assignable user. A user without that permission can't be assigned to issues. And so, when someone leaves the organisation, removing the user's license / access not only frees up license seeds / costs for your organisation, it also makes it impossible to assign that user to issues.

As part of the offboarding process, you can (and maybe even should) pull a list of issues the exiting user is still assigned to and reassign those to someone else.

Hope this helps!