• Search of SMB shares not working (MacOS client)


    CS01-HS
    • Minor

    I don't search often so I can't say for certain it's the beta but it used to work consistently and now it doesn't, even in safe mode. No results returned no matter how long I wait.

     

    I'm running the latest MacOS Catalina.

    I also tested in MacOS Mojave (unraid VM), same result.

     

    I have a Raspberry Pi shared over SMB where search from the same two clients works fine.

     

    Diagnostics from safe mode attached.

     

    nas-diagnostics-20201027-1319.zip

    • Like 1


    User Feedback

    Recommended Comments

    Still a problem in beta-35. 

     

    Am I the only who searches SMB shares or are others not experiencing this?

    Link to comment
    Share on other sites
    1 hour ago, CS01-HS said:

    Am I the only who searches SMB shares or are others not experiencing this?

    Are you referring to Spotlight searches for content that's stored on SMB shares, or to something else?

    Link to comment
    Share on other sites
    2 minutes ago, John_M said:

    Are you referring to Spotlight searches for content that's stored on SMB shares, or to something else?

    No. Just a simple search in the Finder window of a share.

    Link to comment
    Share on other sites

    In case it's not clear from my description here it is in pictures:

     

    787541218_ScreenShot2020-11-17at10_13_46AM.thumb.png.ea7f56875e22456f7bcf6918b7572c66.png

     

    1261269430_ScreenShot2020-11-17at10_14_13AM.thumb.png.a446c736a78ee7e6e376184bb7a29615.png

     

    A search of "debian" in my isos share (which clearly contains it) returns no results.

    Searching the full name debian-10.3.0-amd64-netinst.iso also returns no results.

     

    This problem persisted through the upgrade from beta30 to beta35, and from Catalina to Big Sur.

    Link to comment
    Share on other sites
    40 minutes ago, JorgeB said:

    This looks more like a macOS problem.

    Reasonable assumption but with same MacOSs searches on my Raspberry Pi share (with the standard packages) work properly.

     

    *Website is the Raspberry Pi share.

     

    726850417_ScreenShot2020-11-17at11_35_09AM.thumb.png.9a0537d10dc0067d0bec3ce4fc9f83db.png

     

    1133146506_ScreenShot2020-11-17at11_35_32AM.thumb.png.cf919854217beac267e652fc95eb4288.png

    Link to comment
    Share on other sites
    4 minutes ago, JorgeB said:

    I would say that only confirms it's a problem with that specific computer/OS.

    It happens on multiple computers, from Mojave to Catalina to Big Sur. It worked on all of them with 6.8.3. It broke sometime after I installed the first beta (beta25.)

     

    I'm pretty certain that's the culprit - the question is whether it's a bug in the release or something went wrong during the install process, maybe particular to my setup.

     

    To answer that it'd be helpful to know whether it's working with the beta for anyone on MacOS.

    Link to comment
    Share on other sites
    9 minutes ago, CS01-HS said:

    To answer that it'd be helpful to know whether it's working with the beta for anyone on MacOS.

    Yep, maybe someone else will chime in, I don't have any Macs, only work with them when I get paid to do so at work. 😛

    • Haha 1
    Link to comment
    Share on other sites

    Testing an SMB share on Unraid 6.9.0-beta30 6.9.0-beta35 with macOS High Sierra (the latest my ancient MacBook Pro can run) I see the same as you:

    547500541_ScreenShot2020-11-17at22_55_49.png.073a61820fc2069c9ac8e540ffa01a98.png

    1313346692_ScreenShot2020-11-17at22_56_32.png.f2422e84a028c3b236942a9d229d286f.png

    The three matching files are not being found. However, If I copy the folder to a server running Unraid 6.8.3 and repeat the test, the matching three files are found.

    84096127_ScreenShot2020-11-17at22_56_41.png.8ca6a08ec7ea495dfade9c79872d8aa3.png

    1197170526_ScreenShot2020-11-17at22_57_05.png.6ee454518b36bfcd4df8c4b6cae025b5.png

     

    Edited by John_M
    Corrected Unraid version
    • Thanks 1
    Link to comment
    Share on other sites

    I've done some digging on this - here's what I found.

     

    Mount unraid share system on my mac and check its spotlight status:

    [macbook-pro]:~ $ mdutil -s /Volumes/system
    /System/Volumes/Data/Volumes/system:
    Server search enabled.
    [macbook-pro]:~ $

    But as best I can tell "server search" is not in fact enabled.

     

    Turns out samba 4.12.0 changed this search-related default:

    Note that when upgrading existing installations that 
    are using the previous default Spotlight backend 
    Gnome Tracker must explicitly set "spotlight backend = tracker"
    as the new default is "noindex".

     

    If I add the following to SMB extras:

    [global]
       spotlight backend = tracker

    in addition to this share-specific code:

    [system]
       path = /mnt/user/system
       spotlight = yes

     

    Search works again!

     

    When I check spotlight status I get the following:

    [macbook-pro]:~ $ mdutil -s /Volumes/system
    /System/Volumes/Data/Volumes/system:
    Indexing disabled.
    [macbook-pro]:~ $

     

    Hopefully this is useful toward a general fix.

    I'd rather avoid a custom entry for each share.

    • Like 2
    • Thanks 3
    Link to comment
    Share on other sites

    I just noticed that this was happening to me now that I have upgraded to Unraid 6.9. It's a real bummer that we have to do a work around in the meantime.

     

    My only hesitancy with this workaround is that I know I'll forget to remove the added code instructions once this resolves itself.

     

    I just submitted a feedback/bug report from within Unraid's dashboard and linked back to this post in the bug report. Hopefully the Unraid team pushes out an official patch. 🤞🏼

    Edited by Zer0Nin3r
    Submitted bug report
    • Thanks 2
    Link to comment
    Share on other sites

    After upgrading from Unraid 6.8.3 to Unraid 6.9.1 I immediately encountered the problem described in this thread. macOS connecting via SMB to Unraid share unable to search. I tend to search on filename and file kind from macOS Finder.

     

    I cautiously attempted to apply configuration parameters described in this thread, but unsuccessful returned the Unraid 'SMB extras' field to original text.

     

    It would be great if a future update to Unraid might include feature(s) to more easily configure Samba to support Spotlight search. Otherwise I expect I'll invest some time in to learning more about Unraid Samba implementation and Samba configuration.

    Edited by Maxrad
    Link to comment
    Share on other sites
    On 1/13/2021 at 2:21 AM, CS01-HS said:

     

    in addition to this share-specific code:

    
    [system]
       path = /mnt/user/system
       spotlight = yes

     

    Search works again!

     

    I'm a definite +1 on this thread, it stopped working quite a while ago, and I've been trying to get to the bottom of it for a long time. 

     

    Your answer is a glimmer of hope for me, but I don't know where to put that share specific code? 

    There doesn't appear to be anywhere to put it in the share options on my unraid? 

     

    Link to comment
    Share on other sites

    Put it in Settings -> SMB -> SMB Extras

    You have to stop the array to edit it.

     

    Here's what mine looks like with two shares: Private and Public, but I've customized it enough I forget what's changed from the default. I believe the highlighted lines are the only ones necessary to fix search.

     

    622285943_ScreenShot2021-04-12at11_15_03AM.thumb.png.d1bcadbb68806f9c6c2a1d5f0567bc80.png

    Link to comment
    Share on other sites
    10 hours ago, CS01-HS said:

    Put it in Settings -> SMB -> SMB Extras

    You have to stop the array to edit it.

     

    Here's what mine looks like with two shares: Private and Public, but I've customized it enough I forget what's changed from the default. I believe the highlighted lines are the only ones necessary to fix search.

     

    622285943_ScreenShot2021-04-12at11_15_03AM.thumb.png.d1bcadbb68806f9c6c2a1d5f0567bc80.png

    Nice - thanks for this! 

     

    I tried copying in the entries, but it's still not working (even though Terminal says Indexing is on and doesn't report an error) - Perhaps I'll wait 24 hours and see if spotlight indexes. 

     

    I am getting some errors in the log though, any idea where to start with this? 

     

    -- Paste-- 

    Apr 13 11:19:00 CHASM smbd[5906]: [2021/04/13 11:19:00.522119,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:19:00 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:19:00 CHASM smbd[5906]: [2021/04/13 11:19:00.522159,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:19:00 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:19:02 CHASM smbd[5906]: [2021/04/13 11:19:02.670841,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:19:02 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:19:02 CHASM smbd[5906]: [2021/04/13 11:19:02.670877,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:19:02 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Photos

    Apr 13 11:19:58 CHASM smbd[5906]: [2021/04/13 11:19:58.988604,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:19:58 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:19:58 CHASM smbd[5906]: [2021/04/13 11:19:58.988639,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:19:58 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:20:08 CHASM smbd[5906]: [2021/04/13 11:20:08.789527,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:20:08 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:20:08 CHASM smbd[5906]: [2021/04/13 11:20:08.789583,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:20:08 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:20:32 CHASM smbd[5906]: [2021/04/13 11:20:32.311396,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:20:32 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:20:32 CHASM smbd[5906]: [2021/04/13 11:20:32.311436,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:20:32 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:20:45 CHASM smbd[5906]: [2021/04/13 11:20:45.346181,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:20:45 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:20:45 CHASM smbd[5906]: [2021/04/13 11:20:45.346217,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:20:45 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:22:48 CHASM smbd[5906]: [2021/04/13 11:22:48.626097,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:22:48 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:22:48 CHASM smbd[5906]: [2021/04/13 11:22:48.626131,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:22:48 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:23:25 CHASM smbd[5906]: [2021/04/13 11:23:25.156402,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:23:25 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:23:25 CHASM smbd[5906]: [2021/04/13 11:23:25.156437,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:23:25 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Photos

    Apr 13 11:24:06 CHASM smbd[5906]: [2021/04/13 11:24:06.250267,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:24:06 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:24:06 CHASM smbd[5906]: [2021/04/13 11:24:06.250301,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:24:06 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Photos

    Link to comment
    Share on other sites
    41 minutes ago, BenW said:

    Nice - thanks for this! 

     

    I tried copying in the entries, but it's still not working (even though Terminal says Indexing is on and doesn't report an error) - Perhaps I'll wait 24 hours and see if spotlight indexes. 

     

    I am getting some errors in the log though, any idea where to start with this? 

     

    -- Paste-- 

    Apr 13 11:19:00 CHASM smbd[5906]: [2021/04/13 11:19:00.522119,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:19:00 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:19:00 CHASM smbd[5906]: [2021/04/13 11:19:00.522159,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:19:00 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:19:02 CHASM smbd[5906]: [2021/04/13 11:19:02.670841,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:19:02 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:19:02 CHASM smbd[5906]: [2021/04/13 11:19:02.670877,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:19:02 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Photos

    Apr 13 11:19:58 CHASM smbd[5906]: [2021/04/13 11:19:58.988604,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:19:58 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:19:58 CHASM smbd[5906]: [2021/04/13 11:19:58.988639,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:19:58 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:20:08 CHASM smbd[5906]: [2021/04/13 11:20:08.789527,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:20:08 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:20:08 CHASM smbd[5906]: [2021/04/13 11:20:08.789583,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:20:08 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:20:32 CHASM smbd[5906]: [2021/04/13 11:20:32.311396,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:20:32 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:20:32 CHASM smbd[5906]: [2021/04/13 11:20:32.311436,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:20:32 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:20:45 CHASM smbd[5906]: [2021/04/13 11:20:45.346181,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:20:45 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:20:45 CHASM smbd[5906]: [2021/04/13 11:20:45.346217,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:20:45 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:22:48 CHASM smbd[5906]: [2021/04/13 11:22:48.626097,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:22:48 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:22:48 CHASM smbd[5906]: [2021/04/13 11:22:48.626131,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:22:48 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Productions

    Apr 13 11:23:25 CHASM smbd[5906]: [2021/04/13 11:23:25.156402,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:23:25 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:23:25 CHASM smbd[5906]: [2021/04/13 11:23:25.156437,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:23:25 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Photos

    Apr 13 11:24:06 CHASM smbd[5906]: [2021/04/13 11:24:06.250267,  0] ../../source3/rpc_server/mdssvc/mdssvc.c:1565(mds_init_ctx)

    Apr 13 11:24:06 CHASM smbd[5906]:   mds_init_ctx: Unknown backend 1

    Apr 13 11:24:06 CHASM smbd[5906]: [2021/04/13 11:24:06.250301,  0] ../../source3/rpc_server/mdssvc/srv_mdssvc_nt.c:187(_mdssvc_open)

    Apr 13 11:24:06 CHASM smbd[5906]:   _mdssvc_open: Couldn't create policy handle for Photos

     

    Are you sure there's not a typo in your config?

    I'm afraid I'm out of my depth here.

     

    I can say as far as I'm aware spotlight's not involved in SMB search - it should work immediately.

    Link to comment
    Share on other sites
    1 hour ago, CS01-HS said:

     

    Are you sure there's not a typo in your config?

    I'm afraid I'm out of my depth here.

     

    Yeah - I checked and it all seems OK. 

    I'm also massively out of my depth but REALLY appreciate the help you've given thus far, it's appreciated. 

    It seems there's a bit of a collective *shrug* when it comes to MacOS around the unraid community, so any help is definitely useful. 

     

    I *think* it might be this line: 

     

    Spotlight backend = tracker 

     

    As I've been following the below article since I couldn't get it working, and it's pointing to a spotlight backend using elasticsearch:  

     

    and

     

    This article: https://wiki.samba.org/index.php/Spotlight_with_Gnome_Tracker_Backend

    Seems to suggest that you need to compile and install Gnome Tracker backend (hence specifying the backend for spotlight as 'tracker'

     

    Was that something you installed separately or does Unraid have it included? As that would match up to my error: mds_init_ctx: Unknown backend 1

     

    Anyway - I'm *hoping* elasticsearch works after it's finished indexing, otherwise I'll revert back to this thread again. 

     

     

     

    Link to comment
    Share on other sites
    10 hours ago, BenW said:

    Yeah - I checked and it all seems OK. 

    I'm also massively out of my depth but REALLY appreciate the help you've given thus far, it's appreciated. 

    It seems there's a bit of a collective *shrug* when it comes to MacOS around the unraid community, so any help is definitely useful. 

     

    I *think* it might be this line: 

     

    Spotlight backend = tracker 

     

    As I've been following the below article since I couldn't get it working, and it's pointing to a spotlight backend using elasticsearch:  

     

    and

     

    This article: https://wiki.samba.org/index.php/Spotlight_with_Gnome_Tracker_Backend

    Seems to suggest that you need to compile and install Gnome Tracker backend (hence specifying the backend for spotlight as 'tracker'

     

    Was that something you installed separately or does Unraid have it included? As that would match up to my error: mds_init_ctx: Unknown backend 1

     

    Anyway - I'm *hoping* elasticsearch works after it's finished indexing, otherwise I'll revert back to this thread again. 

     

     

     

     

    That's a way to get spotlight indexing working, I haven't tried it and haven't installed extra libraries.

     

    Have you tried stopping/starting the array?

    If you post your full smb extras maybe someone will spot a problem.

    Link to comment
    Share on other sites

    I modified SMB Extra to:
     

    #unassigned_devices_start
    #Unassigned devices share includes
       include = /tmp/unassigned.devices/smb-settings.conf
    #unassigned_devices_end
    
    [global]
       spotlight backend = tracker
    
    [Media]
       path = /mnt/user/Media
       spotlight = yes

     

    … rebooted Unraid 6.9.2 and spotlight search seems to be working again in macOS Finder over SMB! I haven't  examined logs for potential adverse events but will do in a little while.

     

    Edited by Maxrad
    Added Unraid version.
    • Like 1
    Link to comment
    Share on other sites
    On 1/12/2021 at 7:21 AM, CS01-HS said:

    in addition to this share-specific code:

    
    
    [system]
       path = /mnt/user/system
       spotlight = yes

    Do we have to input share specific folders? Would stopping at '/mnt/user/' allow the spotlight flag to be recursive?

     

    On 4/12/2021 at 8:33 AM, CS01-HS said:

    but I've customized it enough I forget what's changed from the default.

     

    This is what the default looks like:

    #unassigned_devices_start
    #Unassigned devices share includes
       include = /tmp/unassigned.devices/smb-settings.conf
    #unassigned_devices_end

     

    Edited by Zer0Nin3r
    • Like 1
    Link to comment
    Share on other sites
    16 minutes ago, Zer0Nin3r said:

    Do we have to input share specific folders? Would stopping at '/mnt/user/' allow the spotlight flag to be recursive?

     

    The path directive supplies the path for a particular share. Not sure why I have to duplicate it in Extra since it's specified by unraid but it wouldn't work without it.

     

    These are share-specific directives so AFAIK it would only apply to the share whose path is /mnt/user (and creating that share might cause conflicts.)

     

    • Thanks 1
    Link to comment
    Share on other sites


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.