Minyaa JIRA is now upgraded to JIRA 4.3.4 + Minyaa 3.1 !

Minyaa Suite

Worklog type appears different in Workflow transition than in Operations.

Details

  • Type: Support Request Support Request
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Answered
  • Affects Version/s: 2.1
  • Fix Version/s: 2.2
  • Component/s: None
  • Security Level: Public
  • Labels:
    None
  • Environment:
    Windows - Tomcat - MySql - Jira standalone 3.13.1
  • Rank:
    Issue can not be ranked. 
  • Workers:
  • JIRA Release:
    3.13.1

Description

Hi,

We have some doubts regarding worklog type:

1.If we log work on transition, worklog type, has a Default (although we didn´t define one, is the first option).

2.If we log work from Operations ("log Work done" from right panel) worklog type has not have a default value, the first option is "Undefined type".

We would like, if possible, that we could have as an option to make the worklog appears allways as 2. and that it could be mandatory, so people has to indicate allways an specific worklog type without relaying in a default value or leaving it undefined.

Thank you.

Regards.
Marla

Issue Links

This issue is resolved by:
MYAA-722 Default worklog type not used in worklog field Minor Resolved

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Thoulé added a comment - 02/Sep/10 10:24 PM

This issue has been already raised and resolved for next release.

Show
Vincent Thoulé added a comment - 02/Sep/10 10:24 PM This issue has been already raised and resolved for next release.
Hide
Permalink
Marla added a comment - 02/Sep/10 10:37 PM

Thank you Vincent, just as a comment take into account we would rather don't use Default value but a mandatory value without pre-selection, as I understand MYAA-722 ask for the default value to be used.
Regards.
Maria

Show
Marla added a comment - 02/Sep/10 10:37 PM Thank you Vincent, just as a comment take into account we would rather don't use Default value but a mandatory value without pre-selection, as I understand MYAA-722 ask for the default value to be used. Regards. Maria
Hide
Permalink
Vincent Thoulé added a comment - 02/Sep/10 10:42 PM

Ok,

Note that for in a current development for a Client, I will introduce the default value per user.
And it is also planned to implement a default Worklog Type per Worklow Step, but not yet scheduled.

Which of two case will fit with your needs ?
Vincent

Show
Vincent Thoulé added a comment - 02/Sep/10 10:42 PM Ok, Note that for in a current development for a Client, I will introduce the default value per user. And it is also planned to implement a default Worklog Type per Worklow Step, but not yet scheduled. Which of two case will fit with your needs ? Vincent
Hide
Permalink
Marla added a comment - 02/Sep/10 11:15 PM

In our case we use worklog type to indicate some information regarding time cost. our worklog type options include:
1. Maintenance = indicate that the time spent can be considered as maintenance time, part of the maintenance contract.
2.System error = indicate that the time spent should be considered as re-work the user company is not charged with this time.
3. Billable = indicate that the time spent can be billed to the user, is not part of the maintenance contract and it is not a system error, but a new agreement.
and there are two more options.

Options 1 and 2 are the most used, working in an issue we could have time spent that apply for system error and time spent that apply for maintenance.

We could define a default value for option 1. but once we define a default value nobody cares in changing it, that's the reason why we would rather don't have a default value.

If we can make the worklog type mandatory and without default that acts as a reminder, so the people don't forget to complete the data.

In our case we can't take advantage of the default value per user or the worklog type, maybe per workflow step we can find a workaround.

Thank you
Maria

Show
Marla added a comment - 02/Sep/10 11:15 PM In our case we use worklog type to indicate some information regarding time cost. our worklog type options include: 1. Maintenance = indicate that the time spent can be considered as maintenance time, part of the maintenance contract. 2.System error = indicate that the time spent should be considered as re-work the user company is not charged with this time. 3. Billable = indicate that the time spent can be billed to the user, is not part of the maintenance contract and it is not a system error, but a new agreement. and there are two more options. Options 1 and 2 are the most used, working in an issue we could have time spent that apply for system error and time spent that apply for maintenance. We could define a default value for option 1. but once we define a default value nobody cares in changing it, that's the reason why we would rather don't have a default value. If we can make the worklog type mandatory and without default that acts as a reminder, so the people don't forget to complete the data. In our case we can't take advantage of the default value per user or the worklog type, maybe per workflow step we can find a workaround. Thank you Maria
Hide
Permalink
Vincent Thoulé added a comment - 02/Sep/10 11:45 PM

Ok, the solution would be to :

  • let the "Undefined type" value in proposed values when no default value is defined
  • define allowed Worklog Type at workflow or workflow step level level. The "Undefined type" value would have to be exclude from allowed values.

Note that currently, you can define a Meta Attribute in Workflow in order to make required a Worklog Type ... it may response to your need.

The control is performed for Worklog Creation and Update from JIRA Worklog page, Portlet and Worklog CustomField.

Show
Vincent Thoulé added a comment - 02/Sep/10 11:45 PM Ok, the solution would be to :
  • let the "Undefined type" value in proposed values when no default value is defined
  • define allowed Worklog Type at workflow or workflow step level level. The "Undefined type" value would have to be exclude from allowed values.
Note that currently, you can define a Meta Attribute in Workflow in order to make required a Worklog Type ... it may response to your need. The control is performed for Worklog Creation and Update from JIRA Worklog page, Portlet and Worklog CustomField.
Hide
Permalink
Marla added a comment - 02/Sep/10 11:47 PM

Thank you!

Show
Marla added a comment - 02/Sep/10 11:47 PM Thank you!

People

Vote (0)
Watch (0)

Dates

  • Created:
    02/Sep/10 6:47 PM
    Updated:
    02/Sep/10 11:47 PM
    Resolved:
    02/Sep/10 10:25 PM
Bug tracking and project tracking for software development powered by Atlassian JIRA (v4.3.4#620-r152668) | Report a problem
This JIRA site is for demonstration purposes only. Evaluate JIRA - bug tracking software for your team.