Top of the page

Valiantys Blog

Contact

An increasing number of JIRA issues require the setting up of links across several hierarchical levels, resulting in a plethora of issues. You can create this type of organisation with the help of some add-ons. Exocet, for example, provides operations for issue creation and tables listing links between issues. However, none of the existing solutions provide a single view of the whole picture. If we imagine a 3-levels issue architecture, when positioned on the 3rd level issue, a link towards the 2nd level issue will be displayed (provided by JIRA or enriched with Exocet), but we won't have any more information about the 1st level issue. To fill this voide, let's see how to create a dynamic 'breadcrumb'. It will display a hierarchical view of the issue and so allow you the access to the "parents" issues.

+ Continue reading

The relatively recent arrival of Atlassian tools means they are often installed and used in isolation from established mainstream IT. Fair enough. But as the popularity (JIRA, Confluence, etc.) grows from their ease-of-use and flexibility they are soon found delivering business critical services. Victims of their own success, the inevitable happens. For better or for worse, they end up being plumbed in to the mainstream IS. Its at this point we should stand back and consider our approach... Let's take a typical case of a JIRA instance that has evolved and grown in line with changing needs. More often than not, its configuration has become complicated, its performances may be falling short of the mark, and to top it all, no one really knows how to best administer it. To reconfigure it - and ensure it will function well in the future - a governance policy is needed, coupled with a good dose of best practices for its implementation. So, here's a couple examples to ponder.

+ Continue reading

Many JIRA users think that the tool is limited regarding its the level of permissions. Indeed, it is currently impossible to specify native permissions by issue type. This would come in quite useful in, for example, the “Browse projects” permission. In this case, how do you apply this permission to an issue type, or even better, to certain people in a same project? At a glance, it seems like 'mission impossible'. It should come as no surprise then that you may encounter visibility or confidentiality issues. It might even be necessary to restructure one or more JIRA projects in order to segment the content. While you can find several ways to avoid this, most of them will be quite complex to implement and not always an ideal solutions over the long-term. Let’s see how to fill this void with a quick and simple method that is one of the many possible uses of the nFeed add-on.

+ Continue reading
1 2 3 4 5 28