General

Feature Request #44

closed

Ability to assign blocker to for issue outside of project

Added by Troy Vail about 2 years ago. Updated about 2 years ago.

Status:
Closed (Resolved)
Priority:
High
Author:
Troy Vail
Assignee:
Milestone:
-
Start date:
Dec 20, 2023
Due date:
% Done:

100%

Estimated time:
1:00 h

Description

When I created issue #42 and tried to assign it as a blocker to issue #33. An error came up saying that issue #42 was not in the same project as issue #33 and couldn't be assigned as a blocker. It seems this shouldn't be a blocker.

Add

Subtasks


Add

Related tasks

Updated by Max Sessions about 2 years ago

@Troy Vail Explain what you mean by "a blocker"?

Updated by David Canfield about 2 years ago

I believe Troy wishes to relate a task outside of the current project (as blocking) I do not think this is a capability that we can add to Redmine, so I have instructed Troy to simply comment on the ticket and change the status to "On Hold / Waiting" amd reassign the ticket to whomever owns the blocking task or issue -- Hope this makes sense. I am going to close this ticket as unresolved as the feature requested is not available and the instructions given represent a workaround.
Actions #3

Updated by David Canfield about 2 years ago

  • Status changed from Opened to Closed (Unresolved)

Updated by David Canfield about 2 years ago

  • Status changed from Closed (Unresolved) to Closed (Resolved)
  • % Done changed from 0 to 100
  • Estimated time set to 1:00 h
Updated config to allow cross project issue relationships (I didn't now that existed) Changing status to closed (Resolved)

Also available in: Atom PDF