Jira Sub-task Naming Convention

[Rahul Shirwadkar]

Can we customize the naming convention for Sub-task.

For.e.g. - I would like to have something like this.

If Task name is JiraTask-500

I would like to have subtask name as

-  JiraTask-500-001

-  JiraTask-500-002

-  JiraTask-500-003 and so on ... and not create a different Number for each subtask I create.

Currently, when I create a new subtask, I get JiraTask-501 JiraTask-502 and so on..

[John Bayne]

.. I hope you can see these images OK?

BTW, thanks for the prompt response.

If you need me to debug on the system I'll be glad to help out ...

John

[John Bayne]

... if I switch to hierarchy view on this, it fails and then on switch back to network, after a delay I see just this:brokenHierarchy.png

[John Bayne]

Hi there,

we have 4.0.4 active.

Yesterday when I reviewed the feature, I was not able to generate network diagrams at all. After some delay I'd then see just the box for the displayed issue. This morning when I came into the office it was working fine, displaying and toggling between the hierarchy and network display; zooming, etc. All great.

If I view an issue with a larger network then it appear to break down.

E.g.

BugNetwork.png

[Pablo Beltran]

In general, the network graph performance is very good....However, it is a FULL visualization of ALL the linked issues. Therefore if users link lots of issues in a messy way, it could take a while go over all the paths despite there are some optimizations to do it reasonably faster.

What version are you using? Since the 4.0.1 version, support for Epic links visualization was dropped from Network graphs because they bring few business value and it could produce huge graphs which take a long time to be displayed.

There are also some performance optimizations to avoid the plugin consume excessive resources on the Server (mostly CPU) which could make it take over 30% more time to get the graph data and let the Server breath. This is necessary to avoid performance issues on JIRA. As much faster as your server runs, surely such internal performance improvements will work better as they were tuned according to some test performed by some customers.

Once the graph is displayed: how many issues and links are displayed on the graph?