Ticket #5607 (assigned)

Opened 8 years ago

Last modified 5 years ago

Add a way to see why a workspace is not valid for an algorithm

Reported by: Russell Taylor Owned by: Anyone
Priority: minor Milestone: Backlog
Component: MantidPlot Keywords:
Cc: Blocked By:
Blocking: Tester:

Description

The fact that the algorithm dialog's input workspace combo-box only shows valid workspaces is very useful for reducing clutter, but does mean that you can't see why a particular workspace is not valid (unless you go off and try to run it via python). This can be awkward if it's not obvious to the user why it isn't valid. Add some (not too intrusive) mechanism so that a user can find out why invalid workspaces were excluded.

Change History

comment:1 Changed 8 years ago by Nick Draper

  • Owner set to Anyone
  • Status changed from new to assigned

comment:2 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

http://www.mantidproject.org/Release_Notes_2_2_Full_List

comment:3 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to release 2.4

comment:4 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.4 to Release 2.5

Moved at the code freeze for release 2.4

comment:5 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.5 to Release 2.6

Moved to r2.6 at the end of r2.5

comment:6 Changed 7 years ago by Nick Draper

  • Status changed from assigned to new

comment:7 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.6 to Backlog

Moved to the Backlog after the code freeze for R2.6

comment:8 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

bulk move to assigned at the into of the triage step

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​6453

Note: See TracTickets for help on using tickets.