Jump to content

Lyonel

Hornbill Users
  • Posts

    683
  • Joined

  • Last visited

  • Days Won

    25

Posts posted by Lyonel

  1. Hey guys,

    Anybody playing The Division 2 or planning to?

    I am an absolute fan of the franchise and have played too many hours of the first one. It was far from perfect, but I really enjoyed it. Since yesterday (pre-order gold or above editons) or Friday 15th (for normal editions) you can play the sequel. And I have to admit Ubisoft did a fuck*** good job! The Division 2 is everything you would expect, and more! I highly recommend it. Of course it has its bugs and will need adjustments over the next few months. But in comparison to Anthem (another shooter / looter recently available) it is a finished product.

    Let me know your thoughts?

  2. Hi,

    I have a need to report on posts made on timelines. What is the meaning of the number displayed in the table?

    SELECT distinct h_visibility FROM h_buz_activities

    I am looking for a rough translation... I looked on the wiki but could not find anything.

    • 1
    • 10
    • 20
    • 30
    • 35
    • 50
    • 100

    Thank you in advance :)

     
  3. @HHH nobody knows when you follow a request :P

    The only difference in my opinion & experience is that "following" allows you to be notified of any update on a request (notifications + News feed) but you do not have any active role in the resolution of the request. As a "member" you have an active role, visible to all.

    As a team leader, I use the "follow" feature a lot on key / critical requests. It allows me to monitor & control the progress on a real-time basis but not be involved in its resolution.

    As a technical expert, I add myself as "member" when I need to intervene / help my colleagues on a request.

    In summary, the difference is:

    - Follow => Keep on eye on it but don't touch

    - Member => Keep an eye & intervene / help out

    That's just my 2 cents

    • Like 1
  4. @AlexTumber here is a list of fields we would like to have (either custom, or by default). I do appreciate this list might be specific to us, but it could be useful to other customers too (I hope!).

    • Priority [Dropdown | source = list ?]
    • Group / Program [Dropdown | source = list ?]
    • External reference [Textbox single line, similar to Service desk requests]
    • Planned benefits [Amount textbox, similar to budget]

    The next few fields are what would have in an ideal, perfect world. They could be custom fields:

    • Reasons [Textbox multiline]
    • Business options [Textbox multiline]
    • Expected benefits [Textbox multiline]
    • Timescale [Textbox single line]
    • Business [Dropdown | source = list ?]
    • Community [Dropdown | source = list ?]
    • Cost Centre [Textbox single line]
    • PAR / PO reference [Textbox single line]

    All of the suggestions above are based on my knowledge of the current system we use (At Task) and Service Manager application (from a technical standpoint).

    We could also do with 2 more tabs (like we already have for risks & costs): "Issues / Defects" and "Lessons"

    More than happy to discuss it over the phone if need be. :ph34r:

    • Like 1
  5. @AlexTumber any updates on this in-app reporting? Without this, I am having a really tough time selling this solution to my colleagues... Especially as there is currently nothing available around budgeting and resources management...

    • Like 1
×
×
  • Create New...