This one is an example from the Automation library, just change the parent branch to be the linked parent instead. That does not work, I have tried for linked issue but its not checking for all the linked issues even if any one of the linked issue is resolved /closed it Resolves/Closed the Parent Issue. Imho, you can Resolve an issue and then have an automation (usually based on an SLA - "Time to Close after Resolution" which would breach after x amount of time) move the issue to Closed. I always try and look at this as follows: Resolved: According to the person working on the issue the issue is Resolved. Status of an issue can be *Closed* but the Resolution can be *Rejected*. Or Status can be *Closed* but the resolution can be *Duplicate*. When an resolution is set on an issue then you will see an strikethrough across the issue key when the issue is mentioned in the comments in any other issue. The status "closed" generally doesn't mean much That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports (eg. average in progress time per project). And all these are available as gadgets on the dashboard too. Resolved is intended to be used when someone thinks an issue is Done, but someone should review it to make sure it’s really Done. In the Jira Default Workflow the Closed status is also configured to prevent future edits to issues in the Closed status. I have the option to reopen a closed ticket that is on a resolved state (closed state) on but it's not working. The message is received on the ticket but it remains closed. I have the option "Allow tickets on this status to be reopened by end users" set for both statuses (resolved and closed) I'm using: ost v1.10 (new installation e.g.: not an 2. publish the workflow, you can save a copy. 3. Go to issue navigator find all issues that are in status CLOSED and resolution is Unresolved. 4. In the top right corner, you will see Tools click on that bulk change. 5. Select all issues. 6. Choose transition issues -> choose Done fix. Resolved: Assigned to states that represent a solution was implemented, but not yet verified. Generally these states apply to bugs. Work items in a Resolved category state appear on the backlog by default. The Agile tools treat the Resolved category state exactly the same as the In Progress category state. You can use Enhancer Plugin for Jira 's Time between custom fields for this use case. The Time Between Custom Field calculates the amount of time passed between two statuses/events. It can be configured to work against a specific working calendar as well as excluding paused statuses. D1U9.

jira difference between resolved and closed