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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Is Jira metadata automatically captured in submitted issues or does this depend on configuration?

I am creating an issue collector and would like to know if it's same to assume that some metadata (e.g. date submitted) is captured by the system.  Not sure if this depends on how my local instance of instance is configured.  TIA. 

1 answer

1 accepted

0 votes
Answer accepted
Brant Schroeder Community Leader Dec 31, 2020

Olga,

  I am not positive what you mean by meta data.  When an issue is submitted the date created would technically be the date submitted.  There are other fields that are auto populated on creation as well.  If you are hoping to capture information outside of the general fields that are populated when an issue is created you would have to configure it to do that.

Hi Brant, that answers it.  Thank you. I meant to ask whether date created is captured by the system out of the box.  I now see that yes it is.  Any chance you may be able to help with today's question about how to automatically trigger an automation rule to run any time there's a change to a field?  Thank you!! olga

Brant Schroeder Community Leader Apr 30, 2021

@Olga Toverovskaya - Monitoring a change to any field would be difficult as you would need to specify all the fields that you want to watch.  Can you explain a little more about what you are trying to do so I can better understand and recommend a solution?

@Brant Schroeder, really appreciate the quick reply!  Here is the skinny: 

I have a parent-child situation going on with my issues.  End users submit issues through the issue collector, issues are tracked in the parent project and then passed to child projects where development teams work them off.  The issues are cloned as they go from the parent to the child.  That is all working great and the status changes are reflected at both levels (parent and child).  What isn't updated is all the other fields.  So if let's say the dev team creates a sub-task, that sub-task stays at the child level and the sub-task is never reflected in the parent project.  Who knows what else those dev teams will come up with?!  Whatever it is, I would like every change to be automatically reflected in the parent project.  Does that make sense?  I am asking for this because the manager of the parent project needs transparency into every little thing without having to open multiple projects.  I am experimenting with the Updated field.  My hope is that if the date the issue was updated changes, that means the issue was changed in some way, and so the linked issue should be updated.  If you think that will work, how do I say "update the original issue from which the current issue was cloned"?  I'm very new to Jira and really appreciate anything you can suggest.  Thanks in advance. Olga  

Brant Schroeder Community Leader Apr 30, 2021

@Olga Toverovskaya You could use the updated field to initiate an automation. I think this will still be a lot of work.  You should take a look at JSU or ScriptRunner.  They are apps that cost extra but I have used them in the past to keep issues synced.  You might consider looking at a better means of reporting than cloning and syncing.  Cloning and Syncing causes a lot of overhead on the instance and if you create proper dashboards you can have the same insights and help move work forward.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

167 views 6 7
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