Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25067

Custom Start and End date to be set default in plans

XMLWordPrintable

    • 1
    • 6
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be great to have a Custom start and end date field for the plans and by default set the custom field across all new plans that will be created. 

      The Start Date field (System field) available is locked and we cannot set the context to it or control it. So having this different custom field to change the settings for every new plan that would be created.

       

          Form Name

            [JSWSERVER-25067] Custom Start and End date to be set default in plans

            Anden added a comment -

            Adding my vote as well. We leverage custom fields and set these manually on every plan create.

            Anden added a comment - Adding my vote as well. We leverage custom fields and set these manually on every plan create.

            Aakrity Tibrewal added a comment -

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Rik de Valk added a comment -

            This seems like a low-effort high-value feature to me. Allow Portfolio Administrators to set system-wide default start and end date custom fields so that each Plan is created with these fields as scheduling field. 

            Current situation: 

            Companies might decide not to use the Target Start and Target End dates as the default. But every plan that is created will have the Target Start and Target End date configured for scheduling. Users will typically start using the plan as it was created. And they will be very confused due to the mix of date fields (plans using the Target dates while their Jira Software Board shows custom date fields. 

            Users will have to change the scheduling configuration of each individual Plan.  

            Desired situation: 

            A Portfolio Administrator will set the system wide default scheduling fields. After that each plan that is created will get these dates for scheduling. 

             

            Rik de Valk added a comment - This seems like a low-effort high-value feature to me. Allow Portfolio Administrators to set system-wide default start and end date custom fields so that each Plan is created with these fields as scheduling field.  Current situation:  Companies might decide not to use the Target Start and Target End dates as the default. But every plan that is created will have the Target Start and Target End date configured for scheduling. Users will typically start using the plan as it was created. And they will be very confused due to the mix of date fields (plans using the Target dates while their Jira Software Board shows custom date fields.  Users will have to change the scheduling configuration of each individual Plan.   Desired situation:  A Portfolio Administrator will set the system wide default scheduling fields. After that each plan that is created will get these dates for scheduling.   

              Unassigned Unassigned
              c1c38b0b1b95 Priyadharshini CS (Inactive)
              Votes:
              15 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: