Thank you Nicholas, when I get a chance I'll try that.

On May 7, 2017 3:01 AM, "Nicolas Goaziou" <mail@nicolasgoaziou.fr> wrote:
Hello,

Nick Guiffrida <goodfella005@gmail.com> writes:

> Below is content which that can be used to reproduce my problem:
>
> * Job1
>> :PROPERTIES:
>> :job-number: 123457
>> :END:
>> :LOGBOOK:
>> CLOCK: [2017-05-06 Sat 18:59]--[2017-05-06 Sat 19:30] =>  0:31
>> :END:
>> #+BEGIN: clocktable :maxlevel 2 :scope file :properties ("job-number")
>> #+CAPTION: Clock summary at [2017-05-06 Sat 19:54]
>> | job-number | Headline     | Time   |     |
>> |------------+--------------+--------+-----|
>> |            | *Total time* | *0:31* | 0.0 |
>> |------------+--------------+--------+-----|
>> |            | Job1         | 0:31   | 0.0 |
>> #+TBLFM: $4='(org-clock-time% @2$2 $2..$3);%.1f
>> #+END:
>>
>
> You can see that the 'job-number' property is not in the clock table.

The bug doesn't appear in master (i.e., development branch). You may
want to test it or wait for Org 9.1 to be released.

Regards,

--
Nicolas Goaziou