Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
bugzilla
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
etersoft
bugzilla
Commits
d292affc
Commit
d292affc
authored
Mar 29, 2012
by
frase
Committed by
Dave Lawrence
Mar 29, 2012
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bug 643681 - Bug.get should also return the time spent on a bug for users in the timetracking group
r=dkl, a=LpSolit
parent
f21583b6
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
0 deletions
+11
-0
Bug.pm
Bugzilla/WebService/Bug.pm
+11
-0
No files found.
Bugzilla/WebService/Bug.pm
View file @
d292affc
...
...
@@ -886,6 +886,7 @@ sub _bug_to_hash {
# No need to format $bug->deadline specially, because Bugzilla::Bug
# already does it for us.
$item
{
'deadline'
}
=
$self
->
type
(
'string'
,
$bug
->
deadline
);
$item
{
'actual_time'
}
=
$self
->
type
(
'double'
,
$bug
->
actual_time
);
}
if
(
Bugzilla
->
user
->
id
)
{
...
...
@@ -1654,6 +1655,13 @@ the valid ids. Each hash contains the following items:
=over
=item C<actual_time>
C<double> The total number of hours that this bug has taken (so far).
If you are not in the time-tracking group, this field will not be included
in the return value.
=item C<alias>
C<string> The unique alias of this bug.
...
...
@@ -1982,6 +1990,9 @@ and all custom fields.
=item The C<flags> array was added in Bugzilla B<4.4>.
=item The C<actual_time> item was added to the C<bugs> return value
in Bugzilla B<4.4>.
=back
=back
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment