Nic Brough -Adaptavist- Expert

Yes, within it (sometimes it may be a bit over 133) I made a mistake earlier - once you deactivate your site, it will be deleted in 2 weeks, not 30-40 days. At that point, your system is shut down, and the only people who have access to it are Atlassian backup engineers (and even then, not in a directly usable form - the…

There's no trigger for both start and end because it's a really bad idea, it defeats a lot of the points of doing Scrum.

Yes, that's exactly the point. Sub-tasks are not sprint items. They do not go into sprints. They are part of their parent story, not a separate entity. Have another look at the scrum process - there is no "partially done", a sprint item is either done or it is not. Parts of it being done is not relevant and hence their…

Again, it is not a limitation, it supports doing Scrum. Which has nothing to say about sub-tasks; it just talks about sprint items. Sub-tasks are not sprint items, they are parts of sprint items. It sounds like you are estimating it all at the wrong level. If it turns out a component is a sprint item, then it should not be…

Oh, excellent! Well spotted!

It might be. The index is what the search is using, and reconfiguring some stuff (fields mainly) can upset it. Your changes to the names of the links should show when you look at the issues, but I have a feeling they need to be updated in the index as well.

What is the rest of the warning? It usually tells you what the problem is in the warning message.

Yes, thank you. Have you re-indexed the system?

You need to be in edit mode in the workflow, and click on the transition to pop the triggers/conditions/validators/post-functions box up.

Jira Software is built as a Scrum and Kanban tool. In Scrum, you only estimate sprint items as that's where you are committing to a delivery. Sub-tasks are not sprint items, they are fragments of their owning sprint item. In Kanban, the cards are the estimate themselves, and Jira treats sub-tasks as simple cards, there's…

There is no way to do this, the links all get shown on issues. You might try to do it with Behaviours, but it's only going to work in a couple of places, so there's not a lot of point.

Yes, that's why you really don't want to be cloning and moving.

Welcome to the Atlassian Community! Jira administration is there because you've still got the site. You are right in that it is not a product in its own right. If you were to completely delete the site, you would not be able to use it again for months - the name remains active, and backups kept. Why are you trying to…

I'm afraid the labels are for pages, not for content.

Yes, the next thing to check is that you have Scriptrunner installed. Go to Admin -> App management to see it.

What about the other two?

Yes, the archive disappears eventually.

Welcome to the Atlassian Community! Mine uses ingredients as labels, but that works because each page is a recipe. I assume that's not working for you because you're not doing recipe per page. I also use the page tree to very broadly classify recipes, mostly to avoid having too much of one type every week or so. I have…

No, company-managed projects use schemes. If you can't get into the screens then you are not a Jira admin (you may be a project admin, but they can't amend screens or schemes)

Welcome to the Atlassian Community! You can't do this, your reporting would be misleading. Think of Jira searches as having two parts - the search and the report. The search simply finds a list of issues to report on, ones that match the question you have asked. The report then displays the data on the issues that are…

Exactly, they do not allow direct edits back to "empty". It's not going to happen.

It's not, it's a Scriptrunner function.

Welcome to the Atlassian Community! Jira only has one story point field by default, so the other five look like they are calculated metrics that one of your admins has set up. You will need to talk to them about it!

I've only seen it twice (five times if you count the people who messed with the database and got it horribly wrong), so it's pretty obscure!

Technically, the resolution field is not "required" like the other fields can be flagged in Jira's field configuration schemes. It just works a bit differently to other select lists. Most of Jira considers resolution to be the "definition of done". If it is empty, the issue needs attention. If it has any value (including…

Jira Software only supports a single issue type as an Epic, but if you go premium, you can get Advanced Roadmaps, which lets you create more than one issue at the Epic layer (and create layers above). If you do that, go to Admin -> Issues -> Issue types -> Issue type hierarchy -> 

Have you renamed all the options, not just the name of the link?

Welcome to the Atlassian Community! What is the nature of the "hack"? Is it a simple "someone else guessed your password" or "I gave the wrong person access"? Or something else?

All issues that are of a base type are sprint items. Sub-tasks and Epics and layers above Epic are not sprint items, so they are ignored. Sub-tasks are part of their parent, the estimate on the parent is assumed to include any sub-task.

Some of that depends on what scripting and automation apps you have installed, but most of them will work by allowing you to add post-functions into workflows, or create listeners. Go in to edit the workflow where this is happening and look at the transition that has this problem. Check all the triggers, validators (there…