Allow for Fiscal Year date formats to be customized to read FY16 Q1 vs 2015/16 Q1

  • Todd Munnik
  • Sep 2 2015
  • Future consideration
Release time frame
  • Attach files
  • Guest commented
    December 07, 2015 21:09

    This would be really awesome.  EVERYONE (with no exaggeration) who has seen these dates has been confused and gone off into a tangent as to why it makes no sense.

    My personal suggestion would be to allow us to set a 'Fiscal year prefix', so that we could select 'FY', but another company might have a different convention, or show nothing at all. Your UX people may well have a better solution. :)

  • James Field commented
    August 31, 2016 19:58

    Definitely custom - our FY runs Aug to July and having custom fields would be required

  • James Hennig commented
    03 Jan 18:21

    Same issue for our organization - we use a F19Q1 type convention.  We love that we can align the Fiscal Year to our calendar, but like first comment notes it drives confusion.

  • Guest commented
    21 Feb 18:30

    Echo the comments above. There has been lots of confusion around these dates, which ultimately has led to a ton of questions coming to the PM team and taking up a lot of unnecessary time.