Note that sometimes structure generation may time out because of general slowness of Jira caused by other factors. This will cause Structure to try and generate this structure again. If the user clicks "More" link, they can inspect which generators took most of the time.Īny user who can view the structure can resume Automation by clicking Resume button. If the structure contains only dynamic elements, it will appear empty.
The Structure panel will show the " Automation was paused" message and the structure itself will miss the generated content. When Structure app detects that a structure is being generated for an unreasonably long time (by default, 30 seconds), it pauses Automation for that structure. Automation Timeout adds universal protection on top of that by limiting the amount of time Structure app can spend generating a particular structure. Extenders have a maximum number of levels to expand a hierarchy. For example, JQL Inserter offers an option to limit the maximum number of issues it adds to a structure. Some generators already have a considerable level of protection. The Automation Timeout is a safeguard that protects Jira from unintended server loads. As with any powerful and flexible feature, it's possible to unintentionally create an unanticipated load on the Jira server. It gives the user the building blocks – generators – for constructing dynamic structures. The Structure Generators feature is very powerful, and very flexible. Inline editing of the Status field enables users to change an issue's status with a double-click on the Structure gridĢ. Automation Timeout safeguards Jira against excessive load that may result from misconfiguration of Structure generators
0 kommentar(er)
