Versions Compared

Old Version 1

changes.mady.by.user Yasuhiro Kawamura -Ricksoft-

Saved on

compared with

New Version Current

changes.mady.by.user Yasuhiro Kawamura -Ricksoft-

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Revamp the 'Get Started' page and bug fixes

↗️ Improvements

Info

About ACT_AS_USER

Scope

ACT_AS_USER scope allows access to Atlassian Cloud through the app's server, acting as the user operating the app.
By adding this scope to the app, we can implement several improvements that we have not been able to achieve so far.

Examples:

  • Instead of leaving an update history by the app, the update history by the user operating the app will be left in the issue update history.

As of is a scope that grants the app permission to impersonate a user and access Jira.

Info

Why we added the ACT_AS_USER scope to WBS Gantt-Chart for Jira

Currently, in WBS Gantt-Chart for Jira, when editing and saving fields such as the start date on the Gantt chart screen, the history shows that the app updated the fields, making it unclear who actually made the updates to the issues (see attached image).

スクリーンショット 2024-07-17 14.43.00.pngImage Added

By granting the ACT_AS_USER scope, WBS Gantt-Chart for Jira can impersonate the user operating the app when updating issues, thus resolving the above problem.

Furthermore, this scope increases the number of operations that can be performed on the application server side, enabling us to explore different methods for performance improvements.

Info

Manual Update Required

The update to version 1.2.0 , we have not yet made updates to the processes requiring the ACT_AS_USER scope, and we have not provided improvements like the example above. However, we plan to make improvements in future updateswill not be performed automatically.
Your Atlassian Cloud site administrator needs to manually approve the update.

Info

What Happens If You Don't Approve the Update

Version 1.2.0 does not yet implement user impersonation functionality, so you can continue to use WBS Gantt-Chart for Jira without any problems even if you do not approve the update.
However, future releases will gradually add impersonation processing, and if you do not update, errors will occur in the next release, making WBS Gantt-Chart for Jira unusable.

🐛 Bug fixes

  • Error when creating an issue containing a Team field

  • Importing from MS project got different hierarchy

  • Gantt error for filter returing issues from over 50 projects

  • Bug of reloading Gantt exceeds the limit number of issues

  • "Maximum number of displayable issues" setting does not work on the Gantt view screen

  • Can not create subtask for issue in a Sprint

  • The setting color when the JQL is empty is not displayed on the apps view screen

  • The name of Quick Filter & Color is not updated in the delete confirm dialog box after change name