Logging Time and Task Creation Issues

[blackcashmere]

I am using a macOS device.

Logging Issues

I tried using the timer again from the new release. I was only able to reach up til 10s and it was making me log 15 minutes. Is that supposed to be how it works?

Also, I tried going for more than 15 minutes. I tried 16 minutes and it was making me log 30 minutes.

Task Creation Issues

Whenever I try to create a task, this happens:

It just gets stuck. Also, i cannot right click the menu tool to quit. I have to force quit it using activity monitor.

I discovered this a few days ago and I'd really like to be able to use it. This app is much more simple and compact than the others that i have found.

Thank you to the developer for resolving my issue a few days ago btw! I hope all is well.

Many Blessings

[blackcashmere]

Also, if you log out and log in to another account the timer and issues that is running and associated with the previous account will still be visible which I think can be a security issue.

[alexcroox]

Hi @blackcashmere thanks for the feedback. With regards to the rounding of time, our team (who this tool was initially created for) round all our time up to the next 15 minutes. I realise not everyone bills this way and now others are using this I will add something in the settings to configure (or disable) the time rounding.

I'm not sure what could be causing the create task crashing, I certainly can't replicate it on the latest build here. Could you check the logs for me when you see it happen and reply with them?

~/Library/Logs/Jira Timer/log.log

[blackcashmere]

Hi, thanks for responding as well. Here are the logs:

➜ Jira Timer git:(master) ✗ tail -f log.log [2018-09-05 15:43:40.182] [info] [ 'Got worklogs from main process', false, 0 ] [2018-09-05 15:44:17.543] [info] Jira Timer [2018-09-05 15:44:17.548] [info] 1.0.12 [2018-09-05 15:44:19.919] [info] [ 'Api call', '/myself', 'GET' ] [2018-09-05 15:44:19.934] [info] [ 'Requesting worklogs' ] [2018-09-05 15:44:20.150] [info] [ 'App version', '1.0.12' ] [2018-09-05 15:44:20.354] [info] Checking for update [2018-09-05 15:44:24.021] [info] Update for version 1.0.12 is not available (latest version: 1.0.12, downgrade is disallowed. [2018-09-05 15:44:24.023] [info] [ 'updateNotAvailable' ] [2018-09-05 15:44:28.533] [info] [ 'Update of worklogs already in progress' ] [2018-09-05 15:44:32.731] [info] [ 'Got worklogs from main process', true, 0 ] [2018-09-05 15:44:35.328] [info] [ 'Api call', '/project?expand=issueTypes', 'GET' ] [2018-09-05 15:44:41.737] [error] Uncaught TypeError: Cannot read property 'forEach' of undefined

[alexcroox]

Thanks, at what exact point does it seem to crash? Clicking the new task button? Choosing a project? Choosing a task type? Submitting?

[blackcashmere]

Steps to Reproduce:

1. Open Jira Timer.
2. Select "New Task".
3. Wait for Projects list to load.
4. Select a Project from the list.
5. Hangs :(

[alexcroox]

I believe it's crashing here: https://github.com/alexcroox/jira-timer-menubar/blob/master/src/containers/new-task/new-task-container.js#L114

I wonder if the project you are selecting doesn't have any issueTypes against it for some reason. Does it crash selecting any other project?

[blackcashmere]

I tried selecting other projects and it behaves the same way.

As for the issue types, according to the configuration on our Jira instance, there is an issue type scheme applied in the project(s).

[alexcroox]

Could you try this dev build for me: https://cl.ly/810e48a35994

In the logs there will be everything that comes back from the projects API. If you beautify the json you should see something like this:

  [
  {
      "expand": "description,lead,issueTypes,url,projectKeys",
      "self": "https://xxxx.atlassian.net/rest/api/2/project/11200",
      "id": "11200",
      "key": "ADSD",
      "issueTypes": [
      {
          "self": "https://xxxx.atlassian.net/rest/api/2/issuetype/10101",
          "id": "10101",
          "description": "A task that needs to be done.",
          "iconUrl": "https://xxxx.atlassian.net/secure/viewavatar?size=xsmall&avatarId=10318&avatarType=issuetype",
          "name": "Task",
          "subtask": false,
          "avatarId": 10318
      },

Or share here if it's not confidential and I'll check it out for you.

In that dev build should also be a new settings option for setting the time rounding :) Check it out and let me know how you get on.

[blackcashmere]

Hi, I tried the timer setting for rounding off. So far so good. It works great! Thank you :)

I tried creating a new issue with the Dev build, here are what the logs look like:

[2018-09-06 08:43:43.014] [info] Jira Timer
[2018-09-06 08:43:43.022] [info] 1.0.12
[2018-09-06 08:43:45.252] [info] [ 'Api call', '/myself', 'GET' ]
[2018-09-06 08:43:45.273] [info] [ 'Requesting worklogs' ]
[2018-09-06 08:43:45.490] [info] [ 'App version', '1.0.12' ]
[2018-09-06 08:43:45.665] [info] Checking for update
[2018-09-06 08:43:49.715] [info] Update for version 1.0.12 is not available (latest version: 1.0.12, downgrade is disallowed).
[2018-09-06 08:43:49.717] [info] [ 'updateNotAvailable' ]
[2018-09-06 08:43:52.988] [info] [ 'Api call', '/project?expand=issueTypes', 'GET' ]
[2018-09-06 08:43:54.217] [info] [ 'Requesting worklogs' ]
[2018-09-06 08:44:00.065] [info] [ 'Projects',
[
  {
    "self": "https://xxxx.atlassian.net/rest/api/2/project/13230",
    "id": "13230",
    "key": "PTPK",
    "name": "Permission Testing Project: Kanban",
    "avatarUrls": {
      "16x16": "https://xxxx.atlassian.net/secure/projectavatar?size=xsmall&pid=13230&avatarId=10011",
      "24x24": "https://xxxx.atlassian.net/secure/projectavatar?size=small&pid=13230&avatarId=10011",
      "32x32": "https://jxxxx.atlassian.net/secure/projectavatar?size=medium&pid=13230&avatarId=10011",
      "48x48": "https://xxxx.atlassian.net/secure/projectavatar?pid=13230&avatarId=10011"
    },
    "projectCategory": {
      "self": "https://xxxx.atlassian.net/rest/api/2/projectCategory/10012",
      "id": "10012",
      "description": "Projects set up for testing purposes",
      "name": "Testing"
    }
  }
]
[2018-09-06 08:44:00.981] [info] [ 'Got worklogs from main process', true, 0 ]
[2018-09-06 08:44:06.160] [error] Uncaught TypeError: Cannot read property 'forEach' of undefined

I removed some info in the logs about other projects, just putting that out there. They are pretty much the same. But there isn't a block for issueTypes anywhere :(

[blackcashmere]

Our Jira version btw is 6.1.4. Not sure if that's relevant but yeah haha might help :)

[alexcroox]

Strange, your projects must be setup not to use them. I'll look into the new task APIs and check it's OK to post without an issue type, if so I'll check for the lack of issueTypes and allow you to create

[alexcroox]

Tried posting without issueType but it's required... I'll have to find out more info around why your projects may not have issueTypes (yet?).

[blackcashmere]

Ok, thank you. Is there anything you'd like me to check on our end that can help you?

[blackcashmere]

any luck? @alexcroox

[alexcroox]

Not had a chance sorry. Off work for a week and 4 month old baby means I won’t get a chance until I return!

[blackcashmere]

Thats alright, thank you for letting me know. Congrats on the baby! :)

[blackcashmere]

bump

[alexcroox]

I can't find anything specific about it, but in order for this app to work you will need to associate your project with an issue type schema. I was under the impression JIRA had a default one, but maybe that's not the case if you created this project on a new account without touching the settings first. https://confluence.atlassian.com/adminjiracloud/associating-issue-types-with-projects-776636339.html

[blackcashmere]

Upon checking the settings on the project I was able to verify that it did have an Issue type scheme associated :(, we are using a server version. Is that relevant?

[mwoffenden]

We're also seeing the hang upon creation of a new task. It happens right after selecting the project name. We're on Jira Server. Would love to see a fix.