Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to add technical documentation which is integrated with JIRA. Edited

JIRA Enhancements Tickets are used to track user requirements and status of the development work. It makes a lot of sense to link such tickets to related technical documentation, so that when you search, you get results related to Requirements, Development Progress, as well as related changes in the code/Database.

For example, I want to indicate what are the major changes that happened, which program part are affected, and on which server (the host of the source-code). The data entry for such information could be text based and manual. Meaning, it is not necessary that there is a direct soft-link to the back-end source code using a browse button, which will actually connect to SVN (source code repository) for example.

We are using Adobe LiveCycle Server/Workbench/Designer, and the code repository and source code control features are very primitive, and don't work well most of the times. 

We need simple approach to link JIRA Tickets with related technical documentation such as the Server, Application, Folder, Source Code Filename, Function Name, and Variable Names. Also, link the related Database details such as Server, DB Name and Table/Field Details.

What I mean by linking, is adding text to indicate relation to the source-code and Database. Eventually, I might want to get report about affected program parts over that past sprint. This is text based information, and doesn't have to be 100% accurate. Or, find out when a certain table was referenced or modified due to development work and what are the related tickets. See snapshot below to clarify the idea. The Highlighted parts, are the information needed to be linked to JIRA Ticket. 

Also, same thing applies if we use complex source code control like SVN with Eclipse. The system is so complex that it will be hard to find such information when browsing JIRA. We need something similar also when working with Eclipse/SVN or similar platforms.

Appreciate your help and reply.


Adobe LiveCycle Workbench Source Code-trn.png

1 answer

0 votes


If I were I will try play with gitignore file and review the Adobe LiveCycle

Also, ping Adobe for the understand the situation of metadata etc.



Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

227 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you