1. Tempo Avatar Tempo
  2. Prime
  3. servertimesheet
  4. Issues

TimeSheet doesn't show some data.

Issue #1082 on hold
Antonio Colom created an issue

Some people from my company are registering their worklog, and (radomly) some time these worklog is not shown on the Timesheet gadget. But, if I change the number of weeks or the people move the week that are viewing so the data appeared. The data seems well recorded. I attach some images showing that in the day 21-march don't appeared the data with a configuration of gadget.

Comments (78)

  2. Andriy Zhdanov

    Hi Antonio,

    Looks like the problem is in Show Empty Rows option. It's designed to show all issues from selected Filter or Project, for example. But I don't see anything selected in your case.

    Note, you may just need to specify Group instead, or list of users you're interested in.

    Thank you.

  3. Antonio Colom reporter

    Hi Andriy. Note that if I put 3 weeks (or more o less) the gadget woks correctly! But, I also have put a filter and tried again, and don't work with two weeks. I haven't put nor filter nor group because this is a gadget created for the administrator and used by all users of JIRA viewing theis own worklog. Thank you for your attention, but it seems that the problem is in another place.

  5. Antonio Colom reporter

    Hi Andriy. I think that the Time Zones aren't involved. The images were taken yesterday. Today the problem persists. A colleague has the same problem with data from 20, 21 and 22 or march. I have changed the gadget and put 3 weeks, and all is shown correct. Thank you.

  6. Andriy Zhdanov

    Sorry, I don't understand it.

    Do you say that if you put 3 weeks it shows all hours for 20, 21 and 22 march, but if you select 1 week, it still does not show some hours for some days?

    Thank you.

  7. Antonio Colom reporter

    How I said in the first email the problem is detected when I have 2 weeks in the "Number of Weeks" of the configuration of the gadget. It is our configuration by default. When somebody said me that their worklog is not shown, if I change the number of weeks to 3 or other number, different to 2, the data is shown. Also if I use the >> to desplace the view of weeks, the data also appeared.

  8. Andriy Zhdanov

    So is it that hours do not appear straight away when you log work done, but then appear if you use >>?

    Do hours appear straight away if you use 3 weeks?

  10. Andriy Zhdanov

    And how do you log work done? Within the gadget?

    Missing hours should also appear if you do refresh in gadget top right corner menu.

    Then it might be some timing issue, i.e. within 3 weeks displayed, it takes it a bit longer to reload, and thus new entry gets loaded.

  11. Antonio Colom reporter

    Hi Andriy. We use two forms: via gadget or opening the issue and logging work done. It seems there isn't difference. I have revised the data inside the BD and seems perfectly correct with the other that is shown. This problem is ocurring from months ago. I have thougt some time if the problem is causing by the date of calendar but i haven't any justification.

    The problem is not for a moment. It isn't a problem of refresh, because for example, I am seeing the work log of this week and the data aren't shown with 2 weeks and is shown with 3 weeks. Also if I use another gadget configuration the problem is persisted with the same number of weeks and the same data with the same date. For increase the information: I have log work for this week (monday 20, tuesday 21 and wednesday 22). With the gadget with two weeks I see only the data from monday 20th and with the gadget with 3 weeks I see all the days. The same configuration, the same data, the same user, all is the same, except change the number of weeks of the gadget. Thank you for your attention.

  12. Antonio Colom reporter

    Hi Andriy. If you see these two images, you will see that the data is showing differently. In this case I have change the reporting day from today to monday. With Today the data is shown, and with Monday doesn't.

  13. Andriy Zhdanov

    Hi Antonio,

    Could you please clarify exact plugin version, JIRA version, locale and timezone?

    Also could you please check if hours are shown in report using Details link in gadget, in case of missing hours?

    Thank you.

  14. Antonio Colom reporter

    Hi Andriy, here are the data: JIRA Software 7.1.10; JIRA Timesheet 3.0.8; Zona horaria PC: (UTC+01:00) Bruselas, Copenhague, Madrid, París; JIRA Huso Horario por defecto: Predeterminado (Sistema): (GMT+01:00) París;

    In case of missing data, using Details, the hours aren’t shown.

    Thank you.

  15. Andriy Zhdanov

    Hi Antonio,

    I've tried running JIRA 7.1.10 with timezone Europe/Paris and language-country code es-ES, but problem still does not happen to me.

    Am I right thinking that hours are not displayed starting from March 21 and it goes further? So till Friday, hours are still not displayed, now for March 21 - 24?

    Thank you.

  16. Antonio Colom reporter

    Hi Andriy. How I said the problem not ocurr to all people, and some times only in some days. I explain you the situaction today, monday 27th. I attach two images: - Time sheet 8, all the data is shown. I am at another week and the data is well presented. - Time sheet 9, with the exact same gadget, i push <<, so the data from this week is not presented. I have recorded some worklog today and it is shown. So it seems it depends about the day of calendar and the weeks. Thank you.

  18. Andriy Zhdanov

    Hi Antonio,

    So, hours are not shown only for 21-24 of March, in case of Reporting day: Monday, and Number of Weeks: 2, so that End Dat is 26th of March, i.e. the problematic week is the last week in the view. Right?

    We know that hours for these days are shown in case of Number of Weeks: 3, and in case of it is not the last week in the view, but first, as it is today, 27th of March. And hours are shown for 27 of March now.

    By saying that problem does not occur to all people, do you mean that you have one gadget configured on dashboard, that shows your (Antonio Colom) timesheet, and someone (you?) can see hours for 21-24 of March for yourself, but some other people see no hours for that days for Atonio Colom?

    Would it be possible to turn on debug logging in your JIRA as described here: http://www.jiratimesheet.com/wiki/Frequent_Questions.html#Problem_Timesheet_does_not_show_anything ? Then, doing refresh in gadget in case of missing hours, you could collect the following messages:

    Using filter: 
Searching worklogs created since
Worklog ... is not visible
Issue ... did not match filter

    May be some more.

    Please let me know this.

    Thank you.

  19. Antonio Colom reporter

    Hi Andriy. A coleague has problems with his worklog recorded today and with the number of weeks of the gadget equal to three. Seems similar to past week and configured with two weeks. Bye.

  20. Antonio Colom reporter

    Hi Andriy. At reference to the question about "the problem not ocurr to all people": I made (as a administrator) a dashboard for all people with the same gadget (shared to all) [Timesheet 3.png]. This gadget show the worklog for own user. So, some people (for example, I) don't view my worklog, but other people is seeing theis own worklog.

    About debug logging I'm not sure to understand. If I want to use temporal debug, is sufficient to add: log4j.logger.jira.timesheet.plugin to DEBUG. What's the name of logger of Log4j? Please, help me.

  21. Andriy Zhdanov

    Hi Antonio,

    It's mainly log4j.logger.jira.plugin, but it might be good to add log4j.logger.com.fdu.jira.plugin and log4j.logger.jira.timesheet.plugin also.

    Thank you.

  22. Antonio Colom reporter

    I'm sorry. I'm not capable of obtain the debug looging. I have created the three lines you said to me and put they with DEBUG and TRACE. I also have made the change indicated in your URL:

    "Changing the location of the log In the log4j.properties file (located in the JIRA application installation directory): Change the following line: log4j.appender.filelog=com.atlassian.jira.logging.JiraHomeAppender ...to this: log4j.appender.filelog=org.apache.log4j.RollingFileAppender Change the following line to point to the new location of the log file: log4j.appender.filelog.File=atlassian-jira.log"

    and I don't obtain any line of debug in the atlassian-jira.log. We also stop and stard again the JIRA Service.

    What is wrong? Thank you in advance.

  23. Andriy Zhdanov

    Hi Antonio,

    Sorry, changing log file location is not necessary, documentation seems to be a bit misleading. For temporary logging, you just need to add jira.plugin, com.fdu.jira.plugin and jira.timesheet.plugin categories in Administration - System - Troubleshooting and Support - Logging & Profiling with DEBUG logging level.

    If it still does not work, would you like to have a video call by skype, hangouts or anything else, tomorrow or next week?

    Thank you.

  24. Antonio Colom reporter

    I have attached attlasian-jira.log. The last three blocks of information show the results with two errors (I did actualize two times) and the last was shown correctly (moving the week). I hope it will be good. Thank you in advance.

  25. Andriy Zhdanov

    Hi Antonio,

    Looking at last - 1 block, between this is show bad and this is show good, I can see that some issues are skipped because they do not match selected filter. Here are a few last records:

    [j.p.report.timesheet.TimeBaseService] Issue IMI-15077 did not match filter, skipping.
[j.p.report.timesheet.TimeBaseService] Issue ADMJIRA-52 did not match filter, skipping.
[j.p.report.timesheet.TimeBaseService] Issue IMI-15097 did not match filter, skipping.

    Though, I can see similarly ADMJIRA-53 and ADMJIRA-55 are skipped in the most last, i.e. good case.

    I guess this is expected though.

    May be you could attach screen shots of good and at least one last bad case also for the log you've provided?

    I can't get what is shown in good case that is not shown in bad case.

    Thank you.

  26. Antonio Colom reporter

    Hi Andriy. I understand that the situation is confuse. I'll try to explain.

    TimeSheet 11.PNG is "BAD", nothing from days 21-24 march is shown. Time Sheet 12.PNG is "GOOD", data from theses days are shown. Now I noticed that not all data is shown (ADMJIRA-53 AND TIA-63). TimeSheet 13.PNG, another very similar gadget with three weeks, showing data from 21-march to today. THe data from 21-24 march is shown, and appeared more data than before. You must see the total by day.

  27. Andriy Zhdanov

    Hi Antonio,

    The difference between Time Sheet 13.PNG and Time Sheet 12.PNG must be explained by using filter Mis teras in 12, and not using any filter in 13.

    However, I still can't get an idea about missing hours from days 21-24 march in Time Sheet 11.PNG.

    Thank you.

  28. Antonio Colom reporter

    You are right, Andriy. I have bein testing with the filter "Mis tareas" and without it. The problem is the lack of data from days 21-24.

  29. Andriy Zhdanov

    Could you please try if missing hours are shown in excel export? In case of missing hours gadget, click Details link to get Report, and then click Excel View in top right corner.

  30. Antonio Colom reporter

    Hi. The missing hours are not shown in Time Sheet Report and also they aren't shown at Excel report.

  31. Andriy Zhdanov

    Hi Antonio,

    Will it be possible to install custom version of instrumented plugin jar in your environment? I would add additional logging to trace each log entry processed.

    Thank you.

  32. Antonio Colom reporter

    Yes, it's possible, but we only have one instalation in Production. So, we must be very carefully to install and unistall the instrumented plugin.

  33. Andriy Zhdanov

    Hi Antonio,

    Please see jira-timesheet-plugin-3.0.8.1a.jar on repository Downloads tab. I've added two TRACE messages:

    Processing worklog ...
Adding worklog ...

    Caution, it's necessary to turn on TRACE logging level for jira.plugin.report.timesheet package. You may remove other packages added for this case.

    With this change we should hopefully see whether missing worklogs are not shown, or not added, or not even retrieved from DB in case of problem.

    Thank you.

  34. Antonio Colom reporter

    Hi Andriy. Excuse me. I need help. What must do with the jar file? How? Where? I have pushed over your URL and I have downloaded the jar file. I don't known what to do next. Thank you in advance.

  35. Andriy Zhdanov

    Hi Antonio,

    Sorry, you need to install it in Administration - Add-ons - Manage add-ons - Upload new jar.

    Thank you.

  36. Antonio Colom reporter

    Hi. I have installed the new jar and I have put TRACE to the jira.plugin.report.timesheet. But nothing like "Processing worklog" or "Adding worklog" has appeared at the log, that I attach. After the installation I see version of Timesheet=3.0.8.1, not is 1a, but the process of installation finish with a message of ok.

  37. Andriy Zhdanov

    Hi Antonio,

    The latter explains why new log records do not appear, looks like plugin update was not installed properly. May be you can uninstall it and install again, no data will be lost.

    Thank you.

  38. Antonio Colom reporter

    Hi Andriy. Another time you are right. The plugin wasn't well installed. I have uninstalled the plugin and I have installed your jar. The version appears as 3.0.8.1a.

    But, surprise, now I can't reproduce the error. The data are shown well. If you want, I could do the TRACE, but with good results maybe is not necessary. Another option is wait for detecting another situation of error and send you the data.

    I'm very interesting to know your opinion. Thank you very much.

  39. Andriy Zhdanov

    Hi Antonio,

    That's good news! Of course that's very strange, but there is no reason to collect logs in case of no problem, let's wait when problem occurs again.

    Thank you.

  41. Antonio Colom reporter

    Hi Andriy. The problem has reproduced with others days. I attach two images: TimeSheet 21.png, you will see that days 4,5 and 6 from april don't have data. TimeSheet 22.png, with <<-1, you will see the data.

    In the zip file there is the TRACE of process. I thing I did 3 process: one like image 21, another like image 22 and another like image 21. My user login is a01494.

    Thank you for your attention.

  42. Andriy Zhdanov

    Hi Antonio,

    I'm not sure I get clear picture in logs. Looking at screen shots, I decided to chase for missing 1h for ADMJIRA-13 on Apr 6.

    $ grep "Apr 06.*ADMJIRA-13" ~/Downloads/atlassian-jira.log

    Produces 6 records, i.e. 3 pairs of Processing and Adding records.

    But comparing to 0.5h for ADMIRA-13 on Apr 3 as follows:

    $ grep "Apr 03.*ADMJIRA-13" ~/Downloads/atlassian-jira.log

    Produces 10 records, 5 pairs of Processing and Adding records.

    So it's still not clear weather 1h for Apr 6 is not read from database or is just not shown in gadget.

    Additionally I have noticed ClientAbortException IOException: An established connection was aborted by the software in your host machine, though I'm not sure if it may relate to the problem.

    But I would like to clarify, in the morning you said the problem does not occur anymore. So does it mean report contained ADMJIRA-13 1h on Apr 6 for 2 weeks window ending this week? But later today it does not show anymore?

    Thank you.

  43. Antonio Colom reporter

    Hi Andriy. I would like to explain exactly what is ocurring but it isn't easy, because the situation changes. I will try to explain. Yesterday morning after installing the plugin the Time Sheet gadget works well. I have some cases of Time Sheet Gadget: I will focus on two of them: a 3 weeks windows and a 2 weeks windows. When I say that works well is that the data is shown apparently correct. During the morning I was logging work on task from 6-apr, and the gadgets works well. After 12:00 a.m. I refresh the three weeks windows and the data from 4:6/apr dissapeared. I use the << and >> buttons and the data appeared o dissapeared, always with the same results. With the 2 weeks windows the data was shown always well. Today, now, ! repeate the tests. The 3 windows gadget don't show the data from 4:6/apr (except using <<, >>, or changing number of weeks). And, surprise, the 2 windows gadget now don't show the data from 21:24/march you said days before.

    I have repeated many times the same process and the results are similar, forcing with CRTL-F5, Actualize, Log in again, etc. I don't known what to do!

  44. Andriy Zhdanov

    Hi Antonio,

    I see. Could you please try to collect logs again for screens 22 and 21? Just make sure to clear it before, and put marks before each of the two iterations.

    Thank you.

  46. Andriy Zhdanov

    Hi Antonio,

    Now it's clear that data is not loaded, i.e. there are now any records for Apr 06.*ADMJIRA-13 in log for image 21, and the are exactly 2 records in each other case.

    It may be that data is not loaded because of some threshold, i.e. some (latest) worklogs are dropped off when they are loaded from DB, when number of worklogs for the query exceeds some number.

    I will double check if anything has changed in JIRA 7.1.10 in the API used for loading worklogs. But could you also please consider, if there is any special setup in your case that could cause such behaviour? E.g. some caching.

    Thank you.

  47. Antonio Colom reporter

    Hi Andriy. I don't know, but with the case of image 21 I increase the number of weeks to 6 or 7, more issues, more worklogs, more days and the data is shown.

  49. Antonio Colom reporter

    Hi Andriy. Only to increase your knowledge. I attack two images 25 and 26. It's is the same gadget with the same configuration, except I has changed the reporting day from monday to sunday. It's the same laboral period (3 weeks) and the data shown are not the same.

  52. Andriy Zhdanov

    Hi Antonio,

    Logs look good. I just would to ask for one more thing. What is issue id for ADMJIRA-13 for example? You can figure it out just by opening the issue and moving mouse over Edit button, then you should see url in browser status bar, like .../EditIssue!default.jspa?id=10000

    I'm asking because sql.log does not contain resultset for queries, but it has some additional queries for some issues referencing them by issue id.

    Note, in sql.log I can see two queries for worklog corresponding to screenshots as you've specified:

    1. for image 25

      SELECT ID, issueid, AUTHOR, grouplevel, rolelevel, worklogbody, CREATED, UPDATEAUTHOR, UPDATED, STARTDATE, timeworked FROM worklog WHERE (STARTDATE >= '2017-03-19 00:00:00.0' ) AND (STARTDATE < '2017-04-11 00:00:00.0' ) AND (AUTHOR = 'a01494' )

    2. for image 27

      SELECT ID, issueid, AUTHOR, grouplevel, rolelevel, worklogbody, CREATED, UPDATEAUTHOR, UPDATED, STARTDATE, timeworked FROM worklog WHERE (STARTDATE >= '2017-03-26 00:00:00.0' ) AND (STARTDATE < '2017-04-18 00:00:00.0' ) AND (AUTHOR = 'a01494' )

    May be you can also execute first query, and see if you get worklog for ADMJIRA-13 for Apr 06.

    Thank you.

  54. Andriy Zhdanov

    Hi Antonio,

    Thank you a lot for your efforts, at least we can eliminate problem on DB side, I can see missing worklog is returned with worklog query.

    I've also analysed sql.log but did not find anything new, i.e. I can see exactly 7 pairs queries + 1 query for issue 23934 details for image 25 (that corresponds to 7 worklogs shown for ADMJIRA-13), and 6 pairs + 1 (that corresponds to 6 worklogs shown for ADMIJIRA013) for image 27, i.e.:

    SELECT ... FROM jiraissue WHERE ID='23934'
SELECT ... FROM issuelink WHERE DESTINATION='23934'

SELECT ... FROM customfieldvalue WHERE ISSUE='23934'

    Next, I thought, we could try to debug JIRA API used by plugin to retrieve data, but I can't get log working for it. I have tried turning on TRACE level for com.atlassian.jira.ofbiz and org.ofbiz, but I don't see messages logged when I refresh the gadget. May be it will be better in your case, if you want to try it.

    So, I've slightly changed plugin again, two things: 1) the way api is used, 2) log Processing worklog message a bit earlier.

    Please see jira-timesheet-plugin-3.0.8.1b.jar.

    Could you please try it, and if problem still reproduces collect jira.log again for image 25 only. Note, no sql log is needed and no need for log for the case there is no missing hours. Though logging for ofbiz may be turned on.

    Thank you.

  55. Antonio Colom reporter

    Ok. I will do, but we start Easter until tuesday 18th. I'll answer this day. Good holidays.

  58. Andriy Zhdanov

    Hi Antonio,

    Everything looks correct, but unfortunately does not bring anything new, I can still see only 7 pairs of records for ADMJIRA-13, and the last one is for Apr 03. And no log records for ofbiz.

    Sorry, I don't know what I can do else. May be you can ask Atlassian Support for help to clarify if we can get debug logging for com.atlassian.jira.ofbiz or org.ofbiz, and actually ask for any hints how to debug worklog entries not returned by ofBizDelegator.findListIteratorByCondition("Worklog", entityCondition) that produces SQL query like the following, from your logs that corresponds to Image 25, and you have confirmed that query returns needed worklogs when executing it yourself on DB:

    SELECT ID, issueid, AUTHOR, grouplevel, rolelevel, worklogbody, CREATED, UPDATEAUTHOR, UPDATED, STARTDATE, timeworked FROM worklog WHERE (STARTDATE >=  '2017-03-19 00:00:00.0' ) AND (STARTDATE <  '2017-04-11 00:00:00.0' ) AND (AUTHOR =  'a01494' )"

    To reiterate, I think that worklog entries are lost somewhere between SQL engine and OfBizDelegator, and we'd like to figure out how to debug JIRA API in between, on your/customer site.

    Thank you.

  59. Antonio Colom reporter

    Don't you thing that you will get better results doing the query directly to Atlassian? I think you know better the thing you are searching.

  60. Andriy Zhdanov

    It's better if you initiate it and provide SEN, and ask to add me as collaborator, then I can proceed further.

  61. Antonio Colom reporter

    Hi Andriy. I reported to Atlassian this bug, and I have received this answer:

    Hi Antonio, Welcome to Atlassian Support! It seems you need to enable DEBUG logging on 2 classes : 'com.atlassian.jira.ofbiz' and 'org.ofbiz'. This is possible from the Logging and profiling page of JIRA. The 'org.ofbiz' class is already present there and you can add the class 'com.atlassian.jira.ofbiz' in there. As for the logging of SQL queries, please take a look at this article and let me know if that helps to log the SQL queries here. Regards, Ruchi See request details and updates for #GHS-79775 - "TimeSheet plugin doesn't show all data."

    I have put the com.atlassian.jira.ofbiz and org.ofbiz and I have obtained the same results that I sent to you. I don't know what to do!

  62. Andriy Zhdanov

    Hi Antonio,

    Just tell them that you did all this, but did not receive any messages in log, and you've debugged SQL queries already and they are correct and sql result is correct too.

    Also, please ask them to add me to that request.

    Thank you.

  64. Antonio Colom reporter

    Hi Antonio, I am not sure why you are not able to reproduce the issue here. I did look into the Timesheet plugin source code here : OfBizListIterator worklogIterator = this.ofBizDelegator.findListIteratorByCondition("Worklog", entityCondition); try { timebase.worklogCount = 0;

      List<String> excludeProjects = this.configurationService.getExcludeProjects();
  for (GenericValue genericWorklog = worklogIterator.next(); genericWorklog != null; genericWorklog = worklogIterator.next())

    I believe if Andriy Zhdanov could debug this part of the plugin source code and check which entries are reaching the worklogIterator then it might give a better idea on why the issue is occurring. I hope this helps! Regards, Ruchi

  65. Andriy Zhdanov

    Hi Antonio,

    I'm not sure, what looks wrong to Richie. The for statement corresponds to standard for (int i = 0; i < N; i++), because OfBizListIterator does not follow the contract for Iterator, i.e. the next() call does not throw NoSuchElementException but returns a null value if the last element has been reached.

    And this is what we exactly were trying to do with no luck. We tried to check which entries are reaching the worklogIterator, but we didn't get any log messages for OfBizListIterator. All we get, is log messages, a few lines below of the mentioned plugin code, and it's too late, records are not reaching plugin for loop.

    Thank you.

  66. Antonio Colom reporter

    Hi Andriy and Antonio, Allow me to clarify myself. I am not saying that the code here is wrong. The code looks right, however if you can restore customer data on your side and then debug the plugin source code in your source code editor, then you can see which values are actually reaching the loop. That might give us a hint as to where we are missing the data from. After that, we can change the starting week for the Timesheet report (so that the issue is fixed and data starts to show) and debug again to see which values reach the loop. Please let me know if this makes sense. Regards, Ruchi

    Sorry, I don't understand what are demanding Ruchi.

  67. Andriy Zhdanov

    Hi Antonio,

    Sorry for delay. As add-on developer, I'm aware of one way to try, i.e. create JIRA home zip so that I can replay scenario with it on my side, probably, but I'm not sure if this is what Richi suggests, and if it will work at all.

    The other, support zip, is not relevant as to me.

    Thank you.

  69. Antonio Colom reporter

    Good day, Andriy. We haven't heard from you for a while. May I know if you were able to review the previous comment? If you need further explanation or any other clarification, please feel free to get back to us. We are here to assist you. Kind regards, Mohamed Riza

  70. Antonio Colom reporter

    Mohamed Riza31/May/17 9:15 AM Hi, Andriy. Thank you for your patience. We had escalated the issue to our dev team to give further input on the issue. Looking at the JIRA source code, there appears to be no logging in the com.atlassian.jira.ofbiz package, which explains those not showing up in the logs. We would like to know what logs are you after specifically? Kind Regards, Mohamed Riza

  71. Andriy Zhdanov

    Hi Antonio,

    First, I do not recieve comments from the support ticket.

    As for the question, we'd like to find out why worklogItetator does not return worklogs sometimes, and would to get debug logging for underlying implementation, i.e. for OfBizDelegator for worklog entity get query.

    Thank you.

  72. Antonio Colom reporter

    Hi Andriy. I attach the answer from Atlassian:

    Good day, Antonio. Could you try logging for log4j.logger.com.atlassian.jira.ofbiz.LoggingSQLInterceptor. This is managed through SQL Logging panel on Logging and profiling page. Just enable it and you'll get all ofbiz queries in atlassian-jira-sql.log. With regards to org.ofbiz, before enabling DEBUG logging for this package you should also edit WEB-INF/classes/debug.properties setting all properties to true. Kind Regards, Mohamed Riza

  73. Andriy Zhdanov

    Hi Antonio,

    Yes, I have seen this, I do have access to Atlassian support ticket now. Please let me know of you need any assistance with this, or you can try to collect new log?

    Thank you.

  74. Antonio Colom reporter

    Hi. Sorry, yes I need help. I was wrong and I thought that you will do it. My mistake. Two things: - I suppose that I have to add a new package name at the logging with the name: "com.atlassian.jira.ofbiz.LoggingSQLInterceptor". Ok? - I never have edited some configuration file of JIRA. I don't know if is needed to do something more than edit the file (if I can search where to edit). Is needed to reboot the JIRA? Can you give me a bit of text with the changes needed?

    By other hand, resolved the before point, I suppose you want that I execute again the gadget and send the log file. Do you want any others packages name logging? Thank a lot.

  75. Andriy Zhdanov

    No problem, I will try to prepare detailed instructions by the end of next week.

    I assume problem still persists.

    Thank you.

  78. Andriy Zhdanov

    Hi Antonio,

    Sorry, it does not look like it's worth of trying anything else for you yet. I've updated support ticket with my thoughts.

    Thank you.

  79. Log in to comment
Assignee
–
Type
bug
Priority
major
Status
on hold
Component
–
Version
3.0
Votes
1
Watchers
1