Blog

Hello! I'm Takayuki Hirota, developer of Issue Editor for JIRA. 
Fun & fun summer is getting closer! My friend of 25 years and I went out for fishing near where I live on the other day. Ended up catching nothing, but it was such a fun time. 

Well, in the last post, we introduced some basic features such as displaying, editing and saving issues. From this time, I am going to introduce various features of Issue Editor for JIRA in detail for the next couple of editions. Screenshots have been taken in the version of 1.3.1. 

Editing Column Display 

How do we add columns or change the column order? The answers are in the Issue Navigator of JIRA. Issue Editor for JIRA follows the configuration of Issue Navigator. 

After switching the view to the list in Issue Navigator, select a field to display by clicking on Column. 

In Issue Editor for JIRA, for basic search and also advanced search by JQL, "My Defaults" is used. And search by filter, Column Setting is used. 

Sort order of columns can be changed by the column header being dragged and dropped. 

Issue Editor for JIRA supports Custom Field Type however, field type provided by third-party add-ons may not be displayed correctly. In that case, please hide the field in the column configuration of the Issue Navigator. 

Changing the size of Rows and Columns

Summary field and multi-rows text field may show only partial values. In this case, please adjust the row height or column width.

Size of rows and columns can be changed in their headers. 

Moreover, changed values can be shown in the same size from next time after selecting "Save Display Settings" in the menu of Issue Editor for JIRA

Fixing Displayed Columns

When displayed columns are increased, spreadsheet shows a scroll bar on the right side. It is always so convenient to keep information such as Issue Key and Summary to be displayed all the time. 

For example, when these four of Issue Type, Issue Key, Summary, and Status need to be displayed at all times, select the cell on the right side of "Status" and click on "Lock Columns" in the menu.  

Changing the number of displaying rows

You can change the number of displaying rows by clicking the spreadsheet icon on the toolbar. 

"Profile" in the drop-down menu is pointing the Page Size of JIRA Profile. 

Let's have a try!

Issue Editor for JIRA is also published in Atlassian Markplace, and installation could be done quickly as long as JIRA is present. 30 day evaluation licenses are available, so please give it a try! 

Next time, we are going to dive deeply into the more display features in Issue Editor for JIRA . 
See you next time! 

(English Translation by Miyuki Sawada) 

Hello! I'm Takayuki Hirota, developer of Issue Editor for JIRA. 
Now it is May and young leaves are glittering under the sun. In the garden of my house, we cast seeds of loofah so, by the summer comes, the seeds will grow and form a "green curtain" that we are looking forward to!

Well, in the last post, I had written about the overview of Issue Editor for JIRA. 
This time, I am going to show how to proceed with Issue Editor for JIRA after installing it in JIRA. 

Displaying Spreadsheet

There are two ways in displaying the spreadsheet of Issue Editor for JIRA.

One way is to display the spreadsheet in the Issue Navigator screen of JIRA. After Issue Editor for JIRA is installed, on the top right of the screen, a pencil icon appears. Let us press this button. 

Spreadsheet is displayed! 

The other way to display the spreadsheet is from Issue Editor link on the hand panel in the project screen. 

Editing Issues

Double click a cell just like in the spreadsheet software. You can see that the value in the cell can be edited. You can also start editing the spreadsheet by pressing F2. 

Depending on the field type, drop down menu or user picker appears. This part provides existing JIRA users with comfortableness.

Saving

When a cell is edited, a red triangle mark appears on the top left corner of the cell, and the save button turns blue. After editing is done, click on this blue save button. 

It is convenient to be able to edit multiple cells simultaneously as paying attention to other issues. 

Let's give it a try!

Issue Editor for JIRA is also published in Atlassian Markplace, and installation could be done quickly as long as JIRA is present. 30 day evaluation licenses are available, so please give it a try! 

Lastly, in this blog, we have explained about basic features from how to display the spreadsheet to saving the changes. Next time, we are going to go through the display features in Issue Editor for JIRA . 
See you next time! 

(English Translation by Miyuki Sawada) 

 

New UI!

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

Leonardo DiCaprio has been awarded the Best Actor of 2016 Oscar. I would like to talk more about this, however the movie has not yet been released in Japan, so maybe some other time. Among the moves I have seen recently, "THE WALK" and "Odyssey" are the ones I like very much. In both movies, there are challenges and difficulties, the characters cope with, and overcome them, which was very touching. I'm sure this scene can apply to our daily situations at work.

Now let us explain about WBS Gantt-Chart for JIRA 8.3.0.

New UI!

We received quite a few feedback for confusing interface, so the UI will completely change! Seeing is believing. Please take a look.

Basically the UI will be all flat design. The confusing tool bars are minimized and organized. Just for the record, when "Save" was minimized, there was a discussion weather the floppy disk icon was acceptable or not since younger generations probably do not know what a floppy disk is (smile).

User Preferences in Dialog Box

Of all the inquiries from our customers, there are quite a few comments stating that they had no idea where the "user preferences" were so we made it new. First of all, we moved the features that were bottom of the top navigation bar to the operation bar.

Also, enabled the user preferences displayable in dialog boxes so that it will look more natural in WBS Gantt-Chart for JIRA.

Now I want to ask all of you: Have you noticed anything after going through all these screenshots introduced above?

"Recalculate Parents & Children", "Auto Calculate Percent done" and "Cascade Changes" of 3 items have been moved to the user preferences. Since these items are used only occasionally, we decided to put them under the user preferences rather thanthe operation toolbar.

Let's give it a try!

WBS Gantt-Chart for JIRA 8.3.0 has been released with some bug fixes. Please have a try!

Thank you and until next time!

(English Translation by Miyuki Sawada)

Hello! I'm Takayuki Hirota, developer of our new add-on tool for JIRA. 
It has been a nice Cherry Blossom season and we can see a flurry of cherry blossom petals... May I congratulate those who have just entered a school and started a new year at a school. There is an elementary school right in front of my house and I can see very cute first graders with school bags that are much bigger for them to carry. 

Well, in this blog, I am going to introduce our new add-on, Issue Editor for JIRA, just made its debut. 

Excel is powerful

What type of software are you using for project task management or software bug management? Issue management tools such as Atlassian JIRA and Redmine have been gaining recognition, however, it is true that spreadsheet type of software such as Excel has still been a wide use of issue management. 

In spite the fact that Excel does not have specific features for task management or bug management, Excel has been widely used for so long. The reasons are probably Excel does not require special training and also it is already installed in enormous number of computers. 

Needs for Excel like features in JIRA

Even though Excel is commonly used, in order to do a good performance, specialized tools are absolutely must. To proceed with a project smoothly, it is true that a software tool such as JIRA is necessary. What can we do to convince Excel users to understand good and useful points of project management tool by encouraging them to try JIRA? I am sure that project managers and leaders are distressed every day. 

We, Ricksoft, as an Atlassian experts for quite a few years, put thoughts about the feature with our customers. We wish if we could the JIRA interface look just like Excel and JIRA itself easier even for a little bit! 

Issue Editor for JIRA's Debut

Issue Editor for JIRA was developed based on the voices of our customers who were utilizing JIRA in on site. Excel like spreadsheet is placed on the JIRA screen, so you can edit JIRA issues (In JIRA, each task or bug is called "Issue")  just like regular spreadsheets. 

Seeing is believing. 
Please check out this 5-min video.  

Main Features

Here are a list of some main features of Issue Editor for JIRA

  • Display lots of issues in a spreadsheet
  • Narrow down by sorting or filtering
  • In-line editing of various fields
  • Copy and paste to Excel sheet
  • Display hierarchy of epic, stories, and subtasks
  • Copy an issue or create subtasks by right clicking of the mouse
  • Switch parent issues by dragging and dropping an issue
  • Compatible with WBS Gantt-Chart for JIRA of Ricksoft family

And many other features that fulfill the needs. 

Let's try!

Issue Editor for JIRA is also published in Atlassian Markplace, and installation could be done quickly as long as JIRA is present. 30 day evaluation licenses are available, so please give it a try! 

From next time, we are going to focus on one feature of Issue Editor for JIRA in each blog post. 
Until then!!  

(English Translation by Miyuki Sawada) 

<Weak Points of JIRA>

One of the Atlassisan's main products, JIRA is good tool for Developer, however, the views for Manager, has been said "weak". 

As a means of supporting features that the products do not own, Atlassian provides Site for Developers and SDK, and Atlassian Marketplace as a place to release developed software. 

Often, JIRA is used in product-developing project, however, there has been strong demand for the gantt-chart features that managers utilize. Then we enabled the gantt-chart add-on (originally developed by a German engineer) which was at that time provided for free, for the Japanese with Japanese resource.  However, we were in the situation that we had to provide some donation to the engineer since he was Christian otherwise we would've been able to utilize the add-on. So we started thinking about developing our own add-on some day because there were lots of requests for the gannt-chart feature from our customers. 

Then, there was an opportunity to propose gantt-chart feature to one customer and we had only two weeks until the proposal submission deadline. 

<The initial implementation of Gantt-Chart in a short period of time: Encountering Ext Gantt>

In our proposal, of course we could not write something we were not able to do, so decided to check the feasibility. It was 2012 and we had full of web application experiences and knowledge of JIRA, however we had developed only a few small JIRA add-ons. The difficult point was to plot out the specification to implement Gantt-Chart to JIRA without any discomfort and to design formulas in order to display screen-drawing without any collapses. Also, we needed to determine how to propose the feasibility of Gantt-Chart itself in such a short period of time. 

Since JIRA is using jQuery, we thought of leveraging the library of drawings made for gantt-chart. However, there were nothing reliable so we investigated more in a wider area and decided to select a drawing library that was the best among all JavaScript library. Ext Gantt was the one we chose. Ex Gantt is based on ExtJS and we felt comfortable in using Ex Gantt since we had been using it for more than a year. 

< Implementing >

Next, we made sure these points.

  • Gantt-Chart can be plotted with ExtJS+Ext Gant in JIRA
  • JIRA Screen is not collapsed
  • Top navigation is not collapse (Especially this one because if this part were broken, nothing could have been done!)

In particular, Velocity is used to extend JIRA screen. The first step is to migrate the demo screen as an Add-on such as Ext Gantt Guides's Hello World (From html to Velocity). http://www.bryntum.com/docs/scheduling/4.x/?#!/guide/gantt_getting_started

 

html file
<!DOCTYPE html>
<html>
<head>
  <link href="http://bryntum.com/examples/extjs-6.0.0/build/classic/theme-classic/resources/theme-classic-all.css" rel="stylesheet" type="text/css"/>
  <link href="http://bryntum.com/examples/gantt-latest/resources/css/sch-gantt-all.css" rel="stylesheet" type="text/css" />
  <script src="http://bryntum.com/examples/extjs-6.0.0/build/ext-all.js" type="text/javascript"></script>
  <script src="http://bryntum.com/examples/gantt-latest/gnt-all-debug.js" type="text/javascript"></script>
  <script src="synopsys.js" type="text/javascript"></script>
</head>
  <body>
  </body>
</html>

Below is the actual code. It is very simple code, however, we read widely Add-on development documents to reach this point. 

Velocity file
$!webResourceManager.requireResource("...")
<html>
<head>
</head>
<body>
</body>
</html>

When the above code starts to work, the correctness of the designed formula is verified and it will be the phase where features are added. Tasks proceed very well without any problem when some features are added individually. However, when all the features are integrated and are to be tested for a release, additional problems arise. They are called "Combination bug." Those problems won't occur when they are tested one by one, and when one of the new features runs in the specific environment where another feature is tested, the new feature does not work. JIRA is well known for its flexible setting and format, however, very complicated at the same time from the testing perspective. 

On the day before the demonstration of Gantt Chart, we found a bug. It was actually a bug from ExtJS, however, we did not know what the cause was. So we sent the code to the technical support desk of Bryntum and they investigated for only 30 minutes then discovered the cause. (The support desk responded exceptionally fast after we told them it would be needed on the next day.) Then, within another 30 minutes, they sent us the fixed code (of ExtJS code) and it ran correctly that made our demonstration possible. 

< Result >

We registered this product in Atlassian Marketplace as "WBS Gantt-Chart for JIRA". And now WBS Gantt-Chart for JIRA does agile development, has been through version upgrades, and become a product that is always displayed in the top selling add-ons for JIRA.  

Our WBS Gantt-Chart for JIRA is now used in large IT and manufacturing companies, and in not only Japanese but also Overseas big IT, software development companies, and in Universities. Last year, we signed sponsorship for the first time for a Japanese company, in Atlassian Summit 2015, and manned a booth to promote WBS Gantt-Chart for JIRA. 

At the booth, we received a lot of feedback and made our decision about the direction of feature enhancement. We will continue to improve WBS Gantt-Chart for JIRA from now on, too. 

<Lastly: Regarding Add-on Development Business>

 Is it fun to develop Atlassian add-ons? My answer is "YES!".
What do we do to make add-ons software easier? Would users be happy about the improvements? Would new techniques or parts be usable? What do we do about Logic? Overseas Marketing? English support? How many thousands of yen can we sell? Is it going to make good business sense? There are many more things to think about. 

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

On the other day, we decided to put a massage chair in our office. Before actually purchasing, we made sure that the one we were going to buy would fit in our office.. then found out it would not be small enough to go through the doors. I haven't encountered this sort of scene before, so was a little surprised...

Let us introduce WBS Gantt-Chart for JIRA 8.2.0.

Until now, issues with WBS is created based on each link if issues have both epic link and hierarchy link.. Due to that, the same ticket is displayed in a few places.

To resolve this problem, we implemented a feature to set display of epic link. Select "Epic" field in the " WBS Gantt-Chart View Configuration" in WBS Gantt-Chart for JIRA.

When "WBS is displayed based on both epic link and hierarchy link." is checked, just like before, hierarchical structure is created in both epic link and hierarchy link. On the other hand, "WBS is displayed based on only hierarchy link." is checked, hierarchy link is prioritized and epic link is ignored. Due to that, tickets that have the same link will be appeared based on their hierarchy links.

WBS Gantt-Chart for JIRA is available in Atlassian Marketplace. For those who have not yet updated your WBS Gantt-Chart for JIRA, we recommend that you do so!

Thank you and until next time!

(English Translation by Miyuki Sawada)

It has been a little while since Atlassian Summit 2015 was over... Here, I would like to look back how we enjoyed it (smile) This year, Atlassian reached 50,000 customers as Mike Canon-Brooks set this number as a goal when he started Atlassian with Scott Farquar and said that himself in a interview from the anchor in some news program of 2005 (6'50") that was played in Keynote on 4th of November. Wow Mike was very young in the video.. of course, he was still in college! Atlassian Summit has been getting larger and larger and this year, the biggest ever, 2,000 and a few hundred of attendees total were at B1F of Marriot Marquis San Francisco. I could tell that the mail hall for the keynote was so spacious!

Top Selling Expert APAC!

Just like every year, there was an Expert Award Night for Atlassian Experts and Add-on Vendors. Up until last year it was held on the last night of Summit, and this year we had it on the night of Ecosystem Partner Day (2nd of Nov.) which was two days before the first keynote of Nov. 4th. Atlassian called Experts' names one after another for various awards. When Eriko Asaoka, Expert Manager of Japan and Stuart Harrington, Head of Atlassian K.K. went up the small stairs to the stage, we still did not have any idea why they got up there. And when they finally started saying, "Top Selling Expert APAC....", ? ? ? We thought No.1 sales expert in APAC is from Japan??? Then we heard "Ricksoft!!!". At that very moment, we looked at each other and said Yeahhhhhh! Wowwwww! 

(Photographed by Atlassian

 

Other expert companies came up and congratulate to us! 

Our Next Goal is to become a member of "Charlie Club!"

We would like thank all of our customers, and partners who introduced our add-on to their customers. Arigato-gozaimasu! ( *゚ェ゚)*_ _))

The first Ricksoft's Booth in Summit15 

Atlassian Summit 2015 was my fourth Summit to attend and for the first time, we signed up for Silver Sponsorship for the summit booth. Instead of the usual two members (CEO, and myself), there were five of us at Marriott Marquis San Francisco! It seems that our receiving the top selling expert APAC lead more summit attendees to stop by our booth (smile) 

(With Atlassian Expert Team in traditional Japanese "Happi" coats) 

Fastest Growing Partner - TEMPO Partner Day 

On the morning of 2nd of Nov, two of us attended the TEMPO Partner Day. Over there we had no idea that we were going to receive another award! Thank you! 

Already looking forward to Summit 2016! 


Sales & Marketing
Ricksoft Inc. 

 

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

Atlassian Summit 2015 is getting closer, starting 3rd of November. Unfortunately, I will not be there, however, Ricksoft will have a booth through the event. So please do not miss this chance and send us your feedback!

Lets us introduce WBS Gantt-Chart for JIRA 8.1.0.

Compatible with JIRA 7.0

WBS Gantt-Chart for JIRA 8.1.0 is compatible with JIRA 7.0 that has recently been released.

Converting to Ticket template

In a case of Ticket templates creation, the templates are probably newly created after model cases are picked up from the WBS created so far. To be more precise, Tickets are perhaps created one by one in Ticket templates as the existing WBS being referred to, however, it takes a lot of troubles. 

Then, we developed a feature that converts an existing WBS to Ticket templates. It is easy to use the feature. Just right click a ticket to convert to Ticket template, and select "Convert into template." The issue types of the selected ticket are converted to Ticket templates.

To create Ticket templates from an existing WBS as mentioned above, follow the steps below. 

  1. Create a ticket to convert into Ticket template
  2. Copy the tickets to convert into Ticket template
  3. Drag and Drop the tickets copied in 2. onto the ticket created in 1. 
  4. Convert the ticket created in 1. into template

Please leverage this new feature "Convert into ticket template" and create ticket templates easily.

Migrating data including ticket templates

Data migration can be done without a ticket template issue type being added to Issue Type Scheme. 

  1. In the Issue Navigator screen, change the issue type of all the ticket templates to another issue type. 
  2. Migrate the data
  3. "Convert into ticket template" of the tickets of 1. in WBS Gantt-Chart for JIRA

This way, you can migrate the data without having to add a ticket template issue types to the Issue Type Scheme.

We have also other updates such as displaying avatar in the field of Assignee, and fixing the bug that the same date as a holiday could be registered in the calendar. As WBS Gantt-Chart for JIRA 8.1.0 is available in Marketplace, please give it a try.

Thank you and until next time!

(English Translation by Miyuki Sawada)

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

We have not officially made an announcement for this, but we have moved the Installation Guide and the User's Guide of WBS Gantt-Chart for JIRA to the online document site. At this moment, the online documents are not yet fully covered however, will definitely be updated accordingly. You can check our online documents here!

Then, let us introduce the enhancement of "Addtional Columns" and "Ticket Configuration".

Extra Columns are editable 

Since WBS Gantt-Chart for JIRA 7.11.0, in addition to the standard columns such as Planned Dates and Percent Done, Custom Fields and some of the System Fields have been dispalyable on WBS. After the release of 7.11.0, we have received inquiries from our customers asking if Extra Columns can edited, so we implemented this edit feature.

Just as in the standard columns, added columns can be edited by being clicked, and you can save the change by clicking the "Save" button.

Moreover, to be able to edit, The check box of "Yes" needs to be checked for a Field in Column Setting.

Adding System Fields

We added some System fields such as Due Date and Description displayable on WBS Gantt-Chart. And some of those added, will be editable, too.

The rest of the fields, which were not added, we are planning to enable them to be displayed, and edited accordingly.

Ticket Configuration become simpler

In a case of already using JIRA, even though WBS Gantt-Chart for JIRA is installed, sometimes, users have some difficulties at the beginning. The main cause of that is that some of the issue types already added are not set in Ticket Configuration and that is why they are not displayed on WBS.

Also, for a case of already utilizing WBS Gantt-Chart for JIRA, every time an issue type is added, it also needs to be added in Ticket Setting, we have received some feedback that the maintenance is such a burden. 

In order to resolve this sort of problem, we implemented "Ticket Display Mode" in Ticket Configuration. There are two display types in "Ticket Display Mode", "Displaying all issue type mode" and "Displaying specified issue type mode".

 

Displaying specified issue type mode

 

Conventional ticket configuration is called "Displaying specified issue type mode". Only the issue types specified in Ticket Configuration  are shown on WBS, and according to thesettings of each issue type, "Planned Dates, Baseline Dates, Progress, and sub-menu of "Create child ticket are displayed.

Displaying all issue type mode

In the newly added "displaying all issue type mode", all issue type set in JIRA are displayed on WBS. With the default setting,

8.0.0 has already been released. Please leverage this version with the new Version which is now simpler to use.

Thank you and until next time!

(English Translation by Miyuki Sawada)


Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

It has been so hot and humid.. Lately, I have learned about "Frappuccino" of Starbucks and not really sure how to consume whipped cream..
Eat just the whipped cream?
Mix with the coffee frappuccino? 
Drink separately?
I am sure I'm still a Frappuccino beginner (smile)

Now, let me introduce the feature enhancement of the next version 8.0.0 to be released soon.

Displaying Version in Bar

From JIRA 6.0, not only the Release Date but also the Start Date can be set in Version. With this specification, Versions are set to be displayed in bars.

To be more precise, Version is displayed in a bar when the Start Date is set. In a case that the Release Date is set, the bar will be displayed to the Release Date, and when it is not set, then the bar will be displayed as the length of a day. 

The bar will not be displayed when only the Release Date is set. However, regardless of the setting of the Start Date, the milestone is displayed as usual, so it should be able to be utilized in the same way as before.

Now Editable and Deletable! 

In the current WBS Gantt-Chart for JIRA, Versions can be created but not edited or deleted. However, in this new version, Versions will be editable and deletable. 

Name, Start Date and Release Date are the targeted items this time. They will be able to be edited as well as the Tickets.

Also, "Delete" can be selected from the contextual menu just as in Tickets. When a Version is deleted in JIRA, you can switch to another version, however, in WBS Gantt-Chart for JIRA, only the deletion can be performed. After a Version is deleted, the tickets used to be under the deleted version will disappear, so the whole screen needs to be reloaded.

By this edit feature being implemented, when "Recalculate Parents and Children" is checked, the Start Date and Finish Date of the Release Date will be recalculated, too.

Moreover, only the "Project Administrators" can perform the feature of editing and deleting of Versions.

JIRA Version Compatibility

As mentioned at the beginning, the Start Date of Versions is available from JIRA 6.0. Due to that, WBS Gantt-Chart for JIRA will have the minimum Version compatibility as 6.0 (used to be 5.1) For those who are using JIRA 5.1, we recommend that you consider your JIRA instance updated to 6.0 or higher.

More and more exciting features are being planned to join the next version, 8.0.0. So please look forward to them introduced in upcoming blogs!

Thank you and until next time!

(English Translation by Miyuki Sawada)

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

As mentioned in the last blog post, Ricksoft has moved to a much bigger office. Pictures and atmosphere of the new office can be found in our Facebook page! For those who are interested, visit our page!

This time, I am going to introduce the feature enhancement of Scheduled jobs released in 7.13.1.

Compatible with Date Picker, Date Time Picker

In the custom fields to store the aggregate calculate results, Date Picker and Date Time Picker has been able to specified in addition to the fields of Field Type, Text Field and Number Field. With this change, for instance, Planned Dates and Baseline Dates of WBS Gantt-Chart for JIRA are now able to be edited in the Scheduled Jobs.

Visualizing Actual Work Done from Work Log

Although WBS Gantt-Chart for JIRA is a tool to manage plans, we hear that many customers say that they would like to utilize WBS Gantt-Chart for JIRA to verify the actual work. Also, there seem to be many customers who are utilizing the Work Log of the JIRA basic feature as the means of managing the actual work.

Then, we created a scheduled job that calculates the Planned Dates (= actual work done) from the Work Log, although it might be a little off from the fundamental use of WBS Gantt-Chart for JIRA. This scheduled job is a template of "Reflect time tracking", so the job is added from the template just as in "Aggregate time tracking".

To explain the description of aggregate calculation briefly...

  • In the Start Date, the start date of Work Log is reflected.
  • In the End Date, the date that the work day is moved forward for the number of days of "Original estimate" from the above Start Date.
  • In the Progress, "Work ratio" calculated from the Work Log is reflected.

Moreover, hierarchies of tickets are not considered.

Executing "Auto-Calculate Percent Done" in Scheduled Job.

There is a feature, "Auto Calculate Percent Done" in WBS Gantt-Chart for JIRA. It is a very convenient feature and updates the Percent Done of the parent ticket when the percent done is edited on WBS Gantt-Chart.

However, this feature allows editing only on WBS Gantt-Chart for JIRA, so, for example, even if Progress is edited from the issue detail screen of JIRA, Progress of the parent ticket is not updated.

So, a scheduled job is added to reflect such edit of Progress of JIRA issue screen to the parent ticket. There is a template for this, therefore you can add a scheduled job by selecting "Calculate progress".

Precaution for Use

All of the features introduced in this blog save the aggregate calculate results in the custom fields originally built in WBS Gantt-Chart for JIRA. So, even if you edit in WBS Gantt-Chart for JIRA, some jobs will be overwritten depending on the aggregate calculation of the Scheduled job. 

From now on, when using these kinds of templates, we recommend that the fields to store aggregate calculate results be set to "Not Editable". To be more precise, the Planned Dates of Ticket Configuration is set to be "Not Editable".

Moreover, Progress field cannot be set to "Not Editable", so please work around in the actual operations.

Information about Version releases is on the Ricksoft web page, however, it is also very convenient that you can watch in Marketplace and receive notification of Version releases. Please do try!

Thank you and until next time!

(English Translation by Miyuki Sawada)

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

I stopped by Tokyo Big Sight for Software Development EXPO (SODEC) where Ricksoft was introducing Atlassian products with Atlassian Japan KK and attended the Atlassian User Group (AUG) on the other days. In SODEC, I realized that JIRA and Confluence have been recognized more than before, and therefore, applications such as Stash, HipChat and add-ons such as WBS Gantt-Chart for JIRA are the next target to pay attention to. Also, in AUG, was able to listen to the passionate talks of the customers who are actually using JIRA and Confluence, and made a promise to myself that I will contribute more as a developer of WBS Gantt-Chart for JIRA.

In this blog, I am going to introduce another key element of WBS Gantt-Chart 7.13.0.

Want the calculation to be done, but...

Let us say, for instance, there is WBS like below. 

It would be the best if the fields related to Time Tracking of "5.Test" were the total of the fields of the child tickets. There is a feature in Time Tracking of JIRA that calculates the total values, however, only subtasks are calculated, therefore as in this case, when child tickets are not subtasks, this feature is not enabled. So, Time Tracking fields need to be entered manually. This is such a burden to our every day work and easy to make mistakes.

And so, WBS Gantt-Chart for JIRA. will provide you with a feature that calculation is done based on ticket structure.

Let's try Overnight Batch! 

Now let's process Time Tracking calculation mentioned earlier with Overnight Batch.

1.Adding Calculation Field

 First of all, create a field to store calculation results. The Custom Fields below, store the results of calculations done on Scheduled Jobs. 

  • Text Field (< 255 characters)
  • Free Text Field (unlimited text)
  • Number Field

In this process, "Original Estimate", "Time Spent", and "Remaining Estimate" are calculated, so the Custom Fields of the numeric "∑Original Estimate", "∑Time Spent" and "∑Remaining Estimate" are added.

2.Adding Jobs

Next, add a job. A job is a summary of a sequence of a calculation process. 

Select the Schedule section of the WBS Gantt-Chart Admin screen and choose "Aggregate time tracking" from the "Template" menu. Now "Aggregate time tracking" is added to the job list. It is possible to create a job by using "Add" button, however, since it is such a pain in the neck that calculation process is programmed and various configurations are done, it is convenient to utilize the Templates.

In the job, filtering conditions of tickets, users who handle this operation and execution intervals are configured as the object of calculations. Click "Edit" link of "Aggregated time tracking" job and each field can be changed. 

There is a key point here, called "Sleep (sec)". There is a possibility that JIRA resources run out and the performance becomes poor when calculation process is performed consecutively toward enormous amount of tickets. 

Then, the process specified in "Sleep (sec)" is interrupted every time a certain number (50) of aggregated calculation process is done. As a guide, the same interval as the aggregate calculation processing time.

 

3.Fixing Tasks

 

After jobs, tasks are set. Tasks are defined as aggregated calculation process for the specified fields. And this time, we created tasks from the template so, only fields that store aggregated calculation results are set.

 

Click the link of "View" of "Aggregate time tracking" and display the job descriptions and tasks belonging to the jobs. And then, click the "Edit" link in the "Aggregate original estimate" among the three tasks in "WBS Gantt-Chart Task Configuration". Since Tasks now can be edited, select "∑Original Estimate" from the drop down menu of "Field", and "Update" it. As in the same way, set the created custom fields for "Time Spent" and "Remaining Estimate".

 

4.Enabling

 

Jobs and Tasks need to be enabled in order to be executed. 

 

To enable Tasks, just click "Enable" link in WBS Gantt Chart Task Configuration. Enable all three tasks!

As for the Jobs, click "Enable" link in WBS Gantt-Chart Job Configuration. After Job is enabled, Aggregated calculation will be process based on the configuration.

Now, let us see the result that is actually executed.

The execution result is displayed in the "Job". You can check the Time and Success/Failure.

As shown in WBS Gantt-Chart, the aggregate results are reflected on the WBS view.

It happened not to be mentioned in this blog, but you can configure jobs and tasks on your own. Please utilize "Aggregate time tracking" shown above. Also, please look forward to more templates we are going to add!

Thank you and until next time!

(English Translation by Miyuki Sawada)

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

Ricksoft has recently moved to a nicer and bigger office with large windows, refreshing room and great access to a couple of train stations near Otemachi/Tokyo station. With this wonderful change, our team of WBS Gantt-Chart for JIRA will keep making a greater deal of progress.

In this blog, I'm going to explain about Critical Paths that is one of the key elements in this release of 7.13.0 for WBS Gantt-Chart for JIRA.

Displaying Critical Paths

There are some tickets that influences the project completion when it is delayed, on project managements. For example, in a case of the gantt-chart below, when "1. Program1" is delayed, the program completion which is at the end of all successor tickets will be displayed.

As the above example shows, when there are only a few tickets or the project is close to its completion, it is easy to find the influential ticket. However, when there are a lot of tickets, or the project is far from its completion, it becomes difficult to find the influential ticket. "Critical Paths" is the paths displayed in a sequence of tickets with Dependencies so that the factors of project delay will be easy to be identified.

In WBS Gantt-Chart for JIRA, Critical Paths are displayed highlighted when "Critical Paths" on the tool bar is checked.

Using Critical Paths Effectively

There are some tips to utilize Critical Paths effectively.

Load Necessary Tickets

Critical Paths is made from the tickets which have been loaded already. So, please load necessary tickets by expanding nodes.

Arrange Ticket to Show Completion

Critical Paths are made on the tickets with the rightmost Planned End Dates. When there is more than one ticket (with rightmost Planned End Date), Critical Path will be made for each ticket, so more than one Critical Path will be displayed.

In order to avoid this sort of situation, have a ticket to show completion ready. Dependency will be created eventually, connecting to the ticket to show completion.

Checking "Cascade Changes"

In order to check to see if the Tickets to show completion is impacted, and Critical Paths are changed, when the actual delay occurs, the Planned Dates of the depended ticket needs to be fixed. In this type of situation, "Cascade Changes" becomes very handy. It changes the plan of the depended ticket accordingly, including tickets on Critical Path. As a consequence, when there is no impact on the Planned End Date of the completed ticket, there is no problem, and when there is impact, the schedule is going to be reviewed.

Check Critical Path Regularly

When Planned Dates and Dependencies are edited, Critical Paths can be changed. Not only you change them, but also other members can change them, so we recommend that Critical Paths be checked regularly.

As mentioned at the beginning, the latest version of 7.13.0 that includes the Critical Paths introduced in this blog has been released. Please give it a try!

Thank you and until next time!

(English Translation by Miyuki Sawada)

Hi, let me introduce myself, I'm Ryosuke Kumai , developer of Expiry Notification for JIRA.

I will now introduce the new add-on, Expiry Notification for JIRA which Ricksoft has released on Atlassian Marketplace.
The add-on can notify log-in password expiration for JIRA users  if JIRA users are managed by Crowd Internal directory.

First, I introduce why this add-on has been produced.

We can configure  "Maximum Unchanged Password Days" as a condition of password policy when using Internal Directory in Crowd.
If JIRA users whose password have expired login to JIRA, only message "Sorry, your username and password are incorrect - please try again." is shown despite log-in password expiration.

This message annoys both JIRA users and administrators, in the case of my company, our users can't know the cause of not log-in and try to log-in again and again, finally ask the administrators to confirm this cause.

Then, I developed  Expiry Notification for JIRA, the add-on can notify users by E-mail before or after when the log-in password has expired, which resolves this problem without causing a user frustration in our company's JIRA.
So, we've released  Expiry Notification for JIRA for JIRA administrator who annoys the same as us.

This add-on provides you the following features.

  1. You can mail to your users with the remaining days before log-in password expiration and also notify after expiration.
  2. You can configure the frequency with sending the notification mail.
  3. You can customize the notification mail body by defining macros.



As shown 3, the notification mail body can be customized, and if you add the URL which links for password reset, JIRA user who received the mail can reset his password easily.

The URL which included in the notification message as default is linked to the password reset screen of JIRA.
If you manage the password reset by Crowd or you'd like to change the other URL, please change it.  

I hope this add-on can elimate JIRA administrator's dissatisfaction.
Please download  from Try it free within 30 days and try it out!

 

(English Translation by Hanayo Minamisawa)

Hello! I'm Tsutomu Amino, developer of WBS Gantt-Chart for JIRA.

On the other day, I saw "Kazu" (Kazuyoshi Miura) sinking a shot with my own eyes. He is over 48 now and still plays soccer in a professional team which has been inspiring me so much. I myself would like to be a professional in this field, and also would like WBS Gantt-Chart for JIRA to be utilized as long as possible.

Now, we are going to provide a feature of 7.12.0 that enables Ticket Templates to be even easier to use.

Sharing Ticket Templates

Currently, Ticket Templates are designed to be operated as project-specific. Due to that, it is not possible that "Templates in Project A can be used in Project B." In a case that the same type of Ticket Templates need to be used, then the same Ticket Templates as in Project A need to be created in Project B.

So, we are going to make Ticket Templates possible to be used across projects. To be more precise, to share Ticket Templates, a project is specified. Therefore, the Ticket Templates of the project can be utilized in the other projects as shared Ticket Templates.

We recommend that the permission to edit issues in which Ticket Templates are shared, be restricted to users who manage Ticket Templates. By doing this, we can avoid a problem that users who do not have project administrator permission can perform Ticket Template edit from the Issue screen.

Adjusting Planned Dates

When tickets are created from Ticket Templates, the same Planned Dates set in the Ticket Templates are set. Since Planned Dates of Ticket Templates become a thing of the past one after another, Planned Dates had to be adjusted after tickets were created.

In order to skip this one extra step, Planned Dates of tickets are adjusted to match the Planned Dates of the tickets of the selected node.

To be more precise, the Date of the far left of the ticket in the Ticket Template is adjusted to become the same Planned Start Date of the ticket in the selected node. If the Planned Start Date of a ticket in the selected node (including Project, Version, and Ticket Template) is left blank, the Planned Date is adjusted based on Today's Date (depending on the configuration of the Planned Start Date when a ticket is created).

Expanding Field to be Set

Until now, not limited to Ticket Templates, some System Fields such as Component and Affected Version are not copied on WBS Gantt-Chart for JIRA. This time, we reviewed these fields that can be copied.

Basically, based on the rules below, we enable values of the fields to be coped. Now, the extra adjustment tasks will be reduced.

  • System Fields are copied from original tickets
    • Fields related to Workflows as in Status and Resolution are set to be default value
  • Custom Fields are not copied
    • Planned Dates can be copied

Distinguishing Ticket Templates and Tickets under the Ticket Template

At this moment, Ticket Templates, tickets under the Ticket Template and regular tickets are displayed in JIRA Agile boards and Issue Navigator screen. Therefore, Ticket Templates are sometimes edited or deleted by mistake.

Then we prepared a means to distinguish Ticket Templates and tickets under the Ticket Template and regular tickets. It is, templateRelatedTickets in JQL and very easy to use.

issue not in templateRelatedTickets()

The above JQL returns issues that are not Ticket Templates or tickets under the selected node.

On the contrary, when only Ticket Templates and tickets under the Ticket Template need to be extracted,

issue in templateRelatedTickets()

This feature is available in Ricksoft Demonstration Environment as well as dragging & dropping tickets feature introduced in the previous blog post. Please give it a try!!

Thank you and until next time!

(English Translation by Miyuki Sawada)