Customers
User information
 Loading ...
Show article in Knowledge Base

 Owner Export knowledge base Export     SubscribeSubscribe      Show article info

Field description - Current Owner / Owner

 

 

Short description:

 

The Current Owner field represents the user that is currently handling the issue. This user usually changes often, as the issue passes through different steps of the workflow. 

 

 

Details:

 

 

Default name: Current Owner

Terminology variations: None

 

In-Use: Optional. This field can be set to be used in the issue field configuration.

 

Mandatory: Optional. This field can be set as mandatory, but need not be.

 

Data type: A User, which can be an internal user but not a support user.

 

Access restrictions: (Default) Created: "Read/Write" for all internal users, and "No access" for external or support users.  Editing: "Read/Write" for all internal users,  and "No access" for support users.

 

Relationships/Dependencies: 

Project > Settings > General, section "General issue settings":

"Owner group" and "Owner" fields should be dependent: This setting makes these fields dependent on each other, so that setting the Current Owner sets the Owner group, for example. 

 

Status: If you have workflows on the project, then the Current Owner is dependent on the issue Status.

 

 

Affected by these settings: 

 

Project > Settings > Workflow:

Here, you can set who should be the new Current owner when the issue is set to a specific status. It can be a specific user, or the Reporter and/or the Developer of the issue, thus making it possible to automate the passing of the issue between the affected users.

  

Project > Settings > Notifications:

The Current Owner of an issue can be set as a recipient of notifications generated by changes to the issue.

 

General > Settings > Issue configurations > Issue rules.

Current Owner can be used in issue rules, either as a criterion, or being set in the rule action.

 

Use cases: 

Current Owner tells you who has responsibility for the issue at this point. In many cases, you have workflows to automatically transfer ownership of the issue during its "life".


User comments
 Loading ...