+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-1078

Save Chart trading parameters (e.g. stop loss levels) individually for each instrument
action_vote_minus_faded.png
3
Votes
 action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

When you specify and save Chart trading parameters (stop loss levels, trailing stop trigger levels etc.) for one instrument, this affects all other instruments of the same category, even those in other workspaces. I suggest to individually save the parameters for each instrument, or alternatively, for each workspace.
It is absolutely vital to be able to adapt the parameters for each instrument indivdually, due to different tick sizes, prices scales and volatility.
 
 

Steps to reproduce this issue
  1. Open a workspace for "CL" (for example)
  2. Open chart trading bar (full mode)
  3. Specifiy stop loss exit strategy = 20 ticks (for example)
  4. Open another workspace with an instrument of the same category (so if your instrument of step 1 is a Futures contract, then open a different Futures contract, for example "GC".) 
  5. You will notify, that the change in CL has affected GC as well. 
    (If you had opened a non-future instrument in step 4, e.g. FOREX, you would notice that the change in CL did not had an effect)  
  6. Change one of the chart trading parameters of your second instrument (e.g. stop loss = 15 ticks)  
  7. You will notifiy that the change of step 6 for instrument 2 has affected instrument 1 as well.
Comments (0)
icon-mono-settings.png
History
sidebar_collapse.png sidebar_expand.png
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Critical
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates