AdminLaszlo Kosa (Business Analyst, EPAM)

My feedback

  1. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    On the EPAM Jira instances, which use SSO, this was never a problem.

    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    @Bojana Thank you for letting us know - I am happy the problem was solved in the meantime, it would be difficult to investigate if it persisted.

    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Which Jira version didn you experience this? We are trying to reproduce.

    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Are you using SSO with JIRA, or vanilla JIRA login?

  2. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    You can already use rich text formatting in the same way as Jira has introduced it.
    Unfortunately there is no RTF formatter toolbar, you need to enter the escape codes for formatting manually (like _removed from 1.8_ to format it in italic, for example).

  3. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    When you're using "copy to run", just uncheck "Link to Parent". This will prevent the Cloned link to be created.

  4. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Update: We have built a successful prototype, but unfortunately the development team has been rotated out before they could implement it in the release.
    This feature still enjoys top priority.

  5. 11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Previously, Jira behavior prevented us to fit the editors with formatter panels. Recently, Jira introduced this, let us see if we can take advantage of it.

  6. 15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Think of this interface as MS Word or Excel. Those will never display you a dialog box on what you want to do.
    We may add a new key to delete cascaded - like ctrl+backspace. That can have a dialog box confirmation like the one in the Execute panel.
    Also, we need undo functionality. Even with just a 1-step memory, it would improve the ease-of-use.

    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    In the Execute mode, there is a confirmation dialog.
    The Library mode is supposed to be a free editor, confirmation dialogs would make it real hard to use - though I agree that an undo function would be very useful.

  7. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Yes, it makes perfect sense. What I am not entirely sure if this use case is frequent enough to justify the effort - but nevertheless, adding it to the backlog.

  8. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    I still don't like the idea - I deliberately separated test status from Jira issue status, so projects can define, and use any workflow for test issues as they need.
    If I wire test status and issue status together, then I need to fix the workflow (as status names can't be used to identify statuses, only IDs, which can be different in different Jira instances... trust me, it is a mess), and in case the users modify the workflow, the plug-in will cause unexpected crashes even in 3rd party plug-ins.
    This results in a lot of frustration and lost data for the user-base, and a lot of difficult support cases for us - we have similar experiences from the Risk plug-in.

    If your project needs this "link", it is possible to define triggers in Jira, which update the issue status at test status changes. It is similar to DB triggers, and you will need Jira admin rights to define, but the triggers themselves are short. We will help you write the triggers, you just need to get Jira support to install it (if you need it in the EPAM instances).

    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Why is it important for you? You can base JQLs on test status just as well as JIRA statuses.

  9. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    AdminLaszlo Kosa (Business Analyst, EPAM) shared this idea  · 
  10. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    I don't fully understand the problem - are you copying tests to different test runs from the library?
    If that is the case, there is a check-box for "Preserve links",
    "Preserve requirements", and "Preserve links to bugs" separately, so you can fully control this behavior.
    Does this solve your problem?

  11. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    A valid point - unfortunately the case when copying the link is necessary is at least as common as this one.
    Fortunately there is a workaround - select the test(s) top copy, and use the "copy to test run" feature, and select the same test run (or library). This will duplicate the tests, and you have control over copying the links, attachments, tests.

  12. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    About the Mapster, we have a short introduction page here:
    https://kb.epam.com/display/EPMXPMC/JIRA+Mind+Map+plugin
    It is still in a very pre-mature state, only used to display issues and connections, but we have big plans for it.

    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    Wouldn't it be more straightforward to store the requirements in JIRA, so there is a more straightforward way of linking them?
    We already have another plug-in (called Mapster) for displaying links in JIRA in a graphical manner - tracing back requirements using that look much easier.

  13. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    AdminLaszlo Kosa (Business Analyst, EPAM) commented  · 

    On the current "plan" view it is really hard to imagine setting any attributes per test - it would greatly slow down test structure and test creation.
    Originally we had a plan to have a toolbar just like the labels bar on the Work view - so you can set the component by simple drag-and-drop.
    Alternatively, I could imagine a "default selection box" on the plan view - all tests created would have the component (priority, assignee, ...) upon creation by default.
    How do you imagine it to work?

Feedback and Knowledge Base