Add work description field to transition screen

[Marco Sacchi]

We want to be able to add work description field (and not comments field) on a screen presented on transition, but i can't find it on available fields.

I have readed almost all documentation and community posts but no one talk about this specific aspect.

I know that the provided JIRA time tracking support copy of comment content into the worklog description as an option, but we need and want make comments and worklogs separate.

We use JIRA Software (Cloud)

Thanks in advance.

In the below screens:

• the first one is the custom screen,
• the second one is the standard provided time tracking screen.

[Nic Brough -Adaptavist-]

The "work description" is part of the work log, not an issue field.  You have to enter a work log in order to enter the description of the work.

[Marco Sacchi]

Hi Nic,

I'm sorry, I forgot to include a screenshot of the screen configuration.  As you can see I already entered the work log item. This configuration builds the first screen that you see in the post above.

I have also readed about project permissions and anyone can create/modify/delete a work log for now. 

Are there any other configurations that prevent the display of the "work description" element?

[Nic Brough -Adaptavist-]

It's not about configuration.  It's about where data is captured.

The "work description" is a field intended to capture information about the work that is being logged.  The field is part of a data item that is about work that is logged on the issue.  It is not directly a part of the issue.  You can't have a "work description" outside a record of work done - it does not make sense.

[Marco Sacchi]

I think you did not fully understand the previous question, maybe the screen shots in Italian have confused you.

I reformulate in the simplest and clearest way possible: in a screen created to be displayed during a workflow transition is it possible to insert a worklog element (time taken, work description, etc.) as in the screen displayed for time tracking?

If so, which elements must be specified?

Thanks for your time.

[Nic Brough -Adaptavist-]

No, I understood it perfectly.

You are trying to add a "work description" field to a screen that is for updating issue data rather than the work log.  As a work description is part of a work log and not the issue, this request is nonsense.

[Marco Zaccari]

Sorry, Nic,
but refering to the screenshots, the time taken field and the starting time field are (saved) to the issue itself, or in the work log of the issue?

[Nic Brough -Adaptavist-]

On the work log.

[Marco Zaccari]

Exactly, Nic, so the request makes sense.

I try to reformulate the question, maybe we understand each other.

The custom screen:

_________________________________________________________________

Editing the screen:

_________________________________________________________________
Database schema:
(we have already the StartDate and TimeWorked in the custom screen)

[Nic Brough -Adaptavist-]

You don't.

Putting the worklog field on the close screen is a botch that doesn't make sense.

[Marco Zaccari]

It make really sense, because when I close an issue, and I record the time spent working to close the issue, I should describe too the work I made.

So the real problem is the worklog field in custom screens that misses an important info: the worklogbody.

[Marco Zaccari]

instead, this botch actually doesn't make absolutely no sense:


____________________________________________
Important step of the workflow:

____________________________________________
The new status of the issue:

[Stefano Coletta]

I've exactly the same issue as perfectly described by @Marco Zaccari and @Marco Sacchi

As a user, even to me it makes no sense to fill in data on a screen which prompts for work log info and then, when submitting the form, adds a comment with the description of the work instead of filling the the actual worklogbody DB field as highlighed in a previous post.

A user has no other "space" other than the Comment describe what he has done!

I think that a "worklog description" textarea should be really part of the system field "timetracking" and its content added to the relative added worklog entry in the DB.

[Ankit Mathur]

I would like to second Stefano's opinion. This is a really absurd issue that we are facing. We use the worklog description to create a report on how much time was spent doing what.

Do let me know if you guys are using any workaround, since Atlassian seems bent on not solving this :(

Best,
Ankit

[Michael Hönes]

Hello,

I'm facing the same issue. @Nic Brough -Adaptavist- do you have any news on this topic?

[Jan Podgorski]

Our findings are that the "Work Description" is meant to capture specific comments from the "Comments" field entered at the time when "Time Spent" on the issue is logged.  Thus it is not intended to capture the entry in the field directly but it is intended to receive text from the "Comments" field. In a sense it provides the "History" for the entries for the time tracking "Work Log" fields. For example, if you forget to enter the "Time Spent" and enter the comments in the Comments field these will not be captured in the Work Log. 
Reading the comments above, the initial confusion regarding the intent may be arising from the behaviour which exposes the "Work Description" on the Create screen but hides this on the Edit screen.  This leads to to further erroneous assumptions. 
Adaptavist may have further insights on this.