Jack Brickey Expert

Sorry, I did not understand your original post. You can’t create a template within the description field. That is a must-line text field. You can create fields in your Bug template such that it directs the creator as desired of course.

Maybe Cherrington in Shropshire England? Just a guess based on my google investigation on the origins of the children’s rhyme.

Hi Stephan, from what you have shared this doesn’t make sense. Changing the layout of fields would have not impact of the underlying data. Are you sure there was data in the fields for the given issue you are viewing? If so is it possible someone deleted the data? I would run an issue query for all issues in the project…

You could do that via Automation... trigger - issue created condition - Issuetype = bug action - add your text to the Description field or other field as desired

Not within the primary query. It would have to be a separate query for linked issues.

@Daniela Griesinger , I would recommend reaching out to Atlassian Support given the original issue has been marked as resolved. This will allow them to log into you instance, with your permission, and have a look.

So the issue here is that you are on Next-gen and the Reports feature is not enabled. Moreover, as you don’t see Project settings in the sidebar it says that you are not the admin of the project so cannot enable. See if you can find the owner of the project and ask them to enable.

Share a image of what you are seeing

While that is supported in server it is not in cloud unfortunately

I can’t say what has gone wrong TBH. If it was working and suddenly stopped then either the icon is not reachable or possibly some bug. I use my own icons and haven’t seen any issues. Of course as this is Cloud we are likely on different versions. maybe try a new storage location altogether.

You can use your own icons for priorities. As the site admin go to Admin > Issues > Priorities. Click on the edit and in the next screen you will need to provide an icon URL where the icon is stored (provided by you).

Are you sure the workflow has been published? 

You could do as Deepanshu indicates. Version names can be whatever you want.

I would stick with one project and components. The only reason, IMO, to use multiple projects is if you will be releasing the components separately and sprinting separately and the teams will be managed separately.

Yes indeed!

From one of my travels...

Possibly San Diego, CA?

You can use Automation (built into Cloud) to achieve this. Have you looked into this as yet?

Hi Bianca, the most likely reason for this is that you do not have permissions to do so. While NG is designed to allow any user to creat projects (if enabled by admin), Classic projects require admin permission. Do you know your admins? If so I would reach out to them to discuss your needs.

If you are a site-admin click on the cog icon in upper right. Select System and scroll down in the sidebar to shared items and shared filters. In this view you can find the owners of all shared filters.

It will only notify the current Assignee. However, you could add the previous assignee to the Watcher list. If desired you could establish some automation to achieve this.

Agreed

Pyramid of Kheops

yes you can do that too.... project settings > details, at the bottom of that page set the Project Lead and set the Default assignee to "Project lead"

fountain in my back yard.

would have to play w/ it a bit but something like... project = "recurring issues" and description ~"monthly audit" and resolutiondate <= startofday(-25d)

Hi Gina, so you can certainly import issues (tasks) into a project using a CSV file. However, based on your thoughts I wanted to share w/ you some concepts of how Jira works. When you import issues you map csv fields (columns) to fields in Jira issues. Nothing goes into a "board" at least not from an import perspective.…

Hi Rahul, welcome to the Community. There are different ways to handle this. The one method often used is to leverage the Components field and define Component leads. So when creating a new issue if the Component is filled in (dropdown) then the issue will be auto-assigned to the component lead. There are other ways, the…

and as such I recommend editing your answer and removing your emails. :-)

the issuekey as it is commonly referred to is the actual number of the issue - project-#, e.g. ACE-123