Nic Brough -Adaptavist- Expert

Sorry, I should have said - <jira home>/logs/atlassian-jira.log is the first place to look

There's a console based script for setting labels over at https://library.adaptavist.com/entity/update-the-labels-for-an-issue-in-jira - it should be quite easy to adapt to be part of an email handler.

I'm afraid that won't work - it's a Behaviour, not code to be used in a scripted email handler.

When you use "create issue" in general, it will only put an issue into a sprint if you explicitly fill in the sprint field during creation. The buttons are not doing the sprint allocations, you are.

Welcome to the Atlassian Community! How have you been trying to do this? Listener? Post-function?

Welcome to the Atlassian Community! Your Epics should not really have an end date. They are supposed to infer their status (and hence end date) from the content of their stories, which you should be expecting to vary. They are not items you should be estimating or planning against. Having said that, there's nothing wrong…

Welcome to the Atlassian Community! Yes and no. If you have used Confluence as intended, using internal links to other pages like [Space: My page name] , then these will all reflect the new locations. This applies to other systems if you update their application links to the new location as well. But hard-coded urls…

Welcome to the Atlassian Community! Could you explain what this "bizzness time theme" is? Most of us have no time to bother with searching for obscure things just because someone asks about it.

It still doesn't work. Could you try posting it here? There are insert options in the editor here in the community.

Welcome to the Atlassian Community! When your administrator "approves" of an app installation, are they then actually going off and installing and configuring the app for you? App requests are a global thing, not a project thing, and they simply email the admins to tell them you've asked for an installation, 

Ok, so you're talking about the Epic : Story relationship, not story : subtask Your import is failing because 1) you are trying to put an Epic name on a Story. The field does not exist for story-level issues, you can only put an Epic name on Epics 2) you have told it that one of your stories has a parent issue. Stories are…

Welcome to the Atlassian Community! This is what it says it is. One of your administrators has deactivated your account on that Cloud system. You will need to talk to your administrators about getting the access back (and maybe ask them why they did it too)

Welcome to the Atlassian Community! Yes, search for the issues you wish to change, and then use the "bulk edit" option in the tools menu to "edit" the issues. Epic Link is one of the fields you can change in bulk アトラシアンコミュニティへようこそ！ はい、変更する問題を検索し、ツールメニューの[一括編集]オプションを使用して問題を「編集」します。 Epic Linkは、一括で変更できるフィールドの1つです。

That function is significantly less old than this question is. It's also counter-productive - it's an anti-collaboration pattern, and something that should be rarely, if ever, used. Also, the usage of comments in JSM projects is for a different purpose, and this function would be of even less use in JSM.

@Srinatha Tondihal Thank you for documenting the time-line! I would love to see this as a reference article here in the Community, something we can point at when people have questions about deletion!

Welcome to the Atlassian Community! You'll need to ask the person who invited you, or the administrators of the system you were invited to.

Welcome to the Atlassian Community! You should create a new email account for your user. It's terrible practice to re-use email addresses for different people (technically, illegal in a lot of industries and countries)

Welcome to the Atlassian Community! Trials do not last forever, the system was probably archived after you stopped using it for a while. If it was more than 60 days ago (I think it's 60, not sure), you'll probably need to contact Atlassian to . If it was over 120 days ago you last used it, my understanding is that…

>"Sprint cannot be completed as there are incomplete subtasks on the following issues:" >but all of the listed issues have been moved to later/different Sprints Er, why? That's not how Scrum works - you should never move issues to later sprints from an active sprint, it makes nonsense of your procesess. >and are no longer…

It won't open for me.

You can find support under https://support.atlassian.com/contact

This suggests you have a damaged data set somewhere. You'll need to read the application log to get started debugging this.

Welcome to the Atlassian Community! Take a look at https://partnerdirectory.atlassian.com

I don't know what to call out as "cool". I'm interested in architecture, so places like Manchester Town Hall, St Pancras's (now) Renaissance Hotel, Tower 42 when it was the tallest building in London, New York's Guggenheim, top of the World Trade Center, and, and, and. I even went to school in a classic Alfred Waterhouse…

Several. There's no point us telling you which ones - you should not be updating the database directly - that mistake is why you're not seeing changes. You should restore to the backup you took before you messed up your database.

No, you can only have one issue type screen scheme per project. You'll need to create a new one (copy the existing one probably), associate it with the project you want to change, and then change the screen schemes it maps to issues.

Because you really don't want the resolution on any layout screen. JIra shows it automatically on view, as it's a system field, but you don't want to put it on an edit or create screen (controlled by layout) because you would end up resolving issues just by editing or creating them. The only screen you should put…

Welcome to the Atlassian Community! Boards are views of issues, not containers for them. An issue that has a field will always have it, irrespective of how it is viewed. But you can select what fields appear on the cards in a board.

Correct, the CMPs don't yet work that way. I'm sure I've seen the request for it.

It has not changed in 6 years, no.