Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-8751

Work Description Field should be mandatory on the Log Work Operation Screen

    • 2
    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      During the Log Work Done operation, TIME SPENT field is mandatory but the Work Description field is not.
      It would be very nice to have this capability mandatory, if not configurable w.r.t.the contexts/projects: because those informations are so important that developers could not skip them, if they want to.

            [JRASERVER-8751] Work Description Field should be mandatory on the Log Work Operation Screen

            Jānis Šakars added a comment - - edited

            This is f-ing ridiculous - issue opened 18 years ago and there is still no solution - one more reason to migrate away from JIRA

            Jānis Šakars added a comment - - edited This is f-ing ridiculous - issue opened 18 years ago and there is still no solution - one more reason to migrate away from JIRA

            Please add this feature as it's needed. We need to manually go to all the team members and get it corrected for each of the worklog entries that are missed.

            Orfelinda DCunha added a comment - Please add this feature as it's needed. We need to manually go to all the team members and get it corrected for each of the worklog entries that are missed.

            +1

            Asim Hassan added a comment - +1

            joc kie added a comment -

            For God's sake … 17 years and counting. Get it done Atlassian!

            joc kie added a comment - For God's sake … 17 years and counting. Get it done Atlassian!

            +1

            some of our partners pay us based on worklogs and it's mandatory to add a comment. if our guys forget to add the comment, we're not getting paid for the invested time. 

            I know this is none of Atlassian's concern, but if we could make the description field mandatory via a setting, we would completely mitigate this financial risk.

            Andrei Bereczki added a comment - +1 some of our partners pay us based on worklogs and it's mandatory to add a comment. if our guys forget to add the comment, we're not getting paid for the invested time.  I know this is none of Atlassian's concern, but if we could make the description field mandatory via a setting, we would completely mitigate this financial risk.

            This is really required, please Atlassian!

            Maximilian Weißböck added a comment - This is really required, please Atlassian!

            +1

            Albert Macovei added a comment - +1

            Omid H. added a comment -

            +1

            Omid H. added a comment - +1

            Possible to have a look on this ??

            schabotbeaulieu added a comment - Possible to have a look on this ??

            Really needed

            Anabela Brkic added a comment - Really needed

            We really need this function, we do not understand why there is no solution for this.

            Fanni Harnócz added a comment - We really need this function, we do not understand why there is no solution for this.

            Badly needed!!!

            Maximilian Weißböck added a comment - Badly needed!!!

            Sean M added a comment -

            Atlassian, don't arbitrarily decide for us what fields are required and what aren't, or at least tell us why you don't think it should be required and what we should do differently if we find that we do require it.

            Sean M added a comment - Atlassian, don't arbitrarily decide for us what fields are required and what aren't, or at least tell us why you don't think it should be required and what we should do differently if we find that we do require it.

            Thomas Pozzo di Borgo added a comment - - edited

            Same we need really this option please.

            Linked to: https://jira.atlassian.com/browse/JRASERVER-35422

            At least add an option in your new automation rules. It will empoyer your customer to use this new feature and bring to use the possibility to make work description mandatory.

            Thomas Pozzo di Borgo added a comment - - edited Same we need really this option please. Linked to: https://jira.atlassian.com/browse/JRASERVER-35422 At least add an option in your new automation rules. It will empoyer your customer to use this new feature and bring to use the possibility to make work description mandatory.

            @fjodors Could you please provide the JS code that work in announcement banner to make work description field mandatory, if you have one. We are also looking for this functionality.

            Omprakash Thamsetty added a comment - @fjodors Could you please provide the JS code that work in announcement banner to make work description field mandatory, if you have one. We are also looking for this functionality.

            GabrielS added a comment -

            I need also this functionality, asap if possible

            GabrielS added a comment - I need also this functionality, asap if possible

            fjodors added a comment -

            Hi Jan
            As workaround you can add your custom script (e.g. JS code in announcement banner) that rewrites standard work log form submit and makes work description field mandatory.

            fjodors added a comment - Hi Jan As workaround you can add your custom script (e.g. JS code in announcement banner) that rewrites standard work log form submit and makes work description field mandatory.

            Wow! This was created 2009 and still not been implemented. It is hard for managers to see time spent of person that are just blank, they need to approach those users and ask what was done during this time spent.

            Is there a work around we could do to force this as required for a particular project or instance?

            Jan Michael Te added a comment - Wow! This was created 2009 and still not been implemented. It is hard for managers to see time spent of person that are just blank, they need to approach those users and ask what was done during this time spent. Is there a work around we could do to force this as required for a particular project or instance?

            This will be a good feature for big organizations to keep up the work done.

            Bora Erdoğan added a comment - This will be a good feature for big organizations to keep up the work done.

            I would also like to see this feature. It is more or less a necessity for billing purposes.

            Oskar Hanberg added a comment - I would also like to see this feature. It is more or less a necessity for billing purposes.

            AOL on this.

            Some use the Jira Suite plugin for changing what's required during closing of an issue or other status change, but AFAICT, that won't help if work is logged without a status change.

            There's also the 3rd party Kaamelot extension, which based on the comments appears to be very hard to get to work, especially with configurations not matching those of the author.

            Being able to see the fields of the "Log Work Done" screen in the field browser, and change whether they are required or not would be very helpful. That's surely where this configuration change belongs.

            Arthur Hagen added a comment - AOL on this. Some use the Jira Suite plugin for changing what's required during closing of an issue or other status change, but AFAICT, that won't help if work is logged without a status change. There's also the 3rd party Kaamelot extension, which based on the comments appears to be very hard to get to work, especially with configurations not matching those of the author. Being able to see the fields of the "Log Work Done" screen in the field browser, and change whether they are required or not would be very helpful. That's surely where this configuration change belongs.

              Unassigned Unassigned
              b149859fae06 Murat Eksioglu
              Votes:
              123 Vote for this issue
              Watchers:
              57 Start watching this issue

                Created:
                Updated: