| Table of Contents | ||||
|---|---|---|---|---|
|
...
- CSV Import - User should able to upload CSV including user profile data and other users should able to see these profile data on the issue view.
- Workday integration - Users should able to sync user profile data from the Workday system and other users should able to see profile data on the issue view.
- LDAP Intergatigation Interation - Users should able to sync user profile data from the active directory using LDAP and other users should able to see profile data on the issue of view.
- SuccessFactors Integration - Users should able to sync user profile data from the SuccessFactors system and other users should able to see profile data on the issue of view.
...
This app can enable seamless integration between different systems. In future user can sync user profile data from different system and see this information Jira.
Todo Activites:
The To-Do activities for Enhanced User Profile application.
- Complete the import user profile data through CSV
- Complete the sync user profile data from Workday
Technical Implementation :
Technical implementation for the Enhanced User Profile:
- We will use atlasian-connect-spring-boot framework to develop this application
- We will use AUI(Atlassian User Interface) for now and later will replace everything to Atlaskit(R&D to integrate with Spring Boot)
- We will use sample project for reference to build this application
- Atlassian sample project Link: https://bitbucket.org/atlassian/atlassian-connect-spring-boot-samples/src/master/
- Follo-Up Project Link: https://bitbucket.org/dchouksey/app-cloud-follow-up/src/master/
- We will user cloud REST API to perform any operation on Jira cloud
- REST API LINK: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
- REST API LINK: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Draft Timing Plan for CSV User Profile Import V2 (Spring Boot):
This is functionality will be rebuild using Atlassian connect spring boot framework. All backend API needs to rebuild in spring boot for V2 application.
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Sr. No. | Task | Estimations (Hours) | Actual Start Date | Actual End date | Status | Assignee | Remark | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Create project and setup configuration(front end and back end flow) | 8 |
| Ariya | Done | ||||||||||||||
| 2 | Back end code get for CSV file and mapping | 24 |
| Ariya | Done | ||||||||||||||
| 3 | Back end code to create properties using rest API | 16 |
| Ariya | Done | ||||||||||||||
| 4 | Back end code to get user info API by issue key(call issue and user properties API ) | 16 |
| Ariya | Done | ||||||||||||||
| 5 | Code Refactoring,Exception handling and adding loggers | 16 |
| Ariya | Done | ||||||||||||||
| 6 | Fix UI issues after the backed integration | 8 |
| Ariya | Done | ||||||||||||||
| 7 | Testing application with all scenarios | 8 |
| Ariya | Done | ||||||||||||||
| 8 | Total | 80 |
Draft Timing Plan for Workday Integration:
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Sr. No. | Task | Estimations (Hours) | Actual Start Date | Actual End date | Status | Assignee | Remark | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Sample SOAP integration with Spring boot application |
| Dipesh | POC Work | |||||||||||||
| 2 | Workday SOAP integration with Spring boot | Dipesh | POC Work | ||||||||||||||
| 3 | |||||||||||||||||
| 4 | |||||||||||||||||
| 5 | |||||||||||||||||
| 6 | |||||||||||||||||
| 7 | |||||||||||||||||
| 8 | Total |