Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Data set creation, update and deletion via Jira Service Management?


Hello community!


We would appreciate very much your ideas / recommendations on how to further investigate the following use case. 


Current situation

For the services we provide to our client, we need to keep uptodate copies of several thousands data sets / data objects.

All objects have the same set of characteristics, like name, size, etc (in total about 20). 

On a regular basis, our client provides us with flat hierarchy data files (CSV or Excel) for the following requests: 

  • Create a new data object
  • Change characteristics of an already existing data objects
  • Delete a data object


Our goal

We would like to replace the CSV- / Excel-based process. 

Presumably with something build upon Jira Service Management, but we are open for other suggestions as well. 

The volume of changes we need to process at once is relatively small, usually less than 10. No need for bulk edits, to process hundreds of data objects at once.

  • All users would be logged in, thus we know to which business entity they belong. 
  • First step, users shall choose what to do: create / change / delete (see above)
  • Create
    • Basically a selection of text fields, drop-down-menus, single / multiple choices.
    • Except for the text fields all fields shall be based on pre-defined lists / tables stored in an external data source (likely SQL).
    • The data objects are hierarchically structured: thus, selections on early fields need to limit available selections on later fields
  • Change
    • Available data objects to choose from depend on the business entity of the logged-in user. 
    • Upon retrival of the selected object users shall see the current values for each field
    • Next to each field the possibility to provide a new (updated) value. 
    • Again, for each field only pre-defined values shall be allowed. 
  • Deletion
    • Select from a list of available data objects the one to be deleted
  • Additional requirements
    • We as well as our client are located within the European Union. Some of the data object field carry personal identifiable information (PII).
    • Thus compliance with the GDPR is required and most probably we need data residency.

We are open for out of the box solutions build upon Atlassian features alone as well as features provided via marketplace apps. 

Thanks a lot! 


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events