+1 888 340 6572 GET STARTED

Open Feature request MC-2424

Format Instrument/Date "X Days back" setting should exclude holidays

Votes

- No additional actions available

Description

Currently the MC format instruments/date setting doesn't exclude weekday holidays (in exchange settings list) when counting days back like it does weekends. I always keep the setting at 2 days back, but have to change it to 3 days back when a holiday comes along, which is rather tedious on multiple charts. Please vote to have this integrated into the Format Instruments/Date window on charts and/or Portfolio Trader.

Comments (1)

Toggle system-generated comments

Chris (Chris)

Christian Spencer
Last seen online at May 17, 2023 - 08:49
Show user details

Jan 10, 2023 - 12:50

This seems to relate to charting, but I want to add a different aspect wich "suffers" the same problem:
I find it not perfect how to schedule data reloads. If due to duration of historical reloads one has to reload in two-day increments, then this doesnt fit on every sunday or when a holiday occurs. A solution in Data-Manager would be, to setup different tasks....wich gets confusing.

Maybe a button "+one on sundays" or something like is possible.

As for holidays as mentioned in the original request, this would not help... but would be nice in Data-Manager ;-)

Reply to comment #1

Comment visibility (whether to hide this comment for "regular users")

Selected syntax: Markdown ▼

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in MarkdownFormatting.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples in tags.
See more formatting tips in WikiFormatting.

or cancel

History

Issue basics

Type of issue

Feature request Unknown issue type
Issue label

No label set
Category

Not determined
Targeted for

Not determined
Status

Under Review

Status not determined
Progress
Priority

Not determined

Affected by this issue (0)

There are no items

People involved

Posted by
automaton (automaton)

automaton
Last seen online at Feb 18, 2020 - 02:50

Show user details
Owned by

Not owned by anyone
Assigned to

Not assigned to anyone
Subscribers

1 subscriber(s)

Click here to show the list of subscribers

Times and dates

Posted at

Apr 09, 2018
Last updated

Apr 10, 2018
Estimated time

Not estimated
Time spent

No time spent

Click here to see time logged against this issue

Issue details

Resolution

Not determined
Reproducability

Not determined
Severity

Not determined

Attachments (0)

There is nothing attached to this issue

Commits (0)

There are no code checkins for this issue

Child issues (0)

This issue does not have any child issues

Duplicate issues (0)

This issue does not have any duplicates