Comments
-
Ok, so lets focus on "In Jira, the field named 'Summary' is used where on the JIRA UI page and how? When I look at a task / bug / epic etc... on the JIRA page, WHERE is the Summary? And for that matter, Where is the Title? Is there a Subject?" The field summary is usually used to contain a summary of the issue. On a Jira…
-
I'm not sure I can tell you any more than "remove the resolution field from the screen". See https://confluence.atlassian.com/adminjiraserver/defining-a-screen-938847288.html for amending screens.
-
Stop looking at the directories, they're not intended to be used like this. The only thing you should be doing with the directories is backing them up. They're not there for you to read outside the application.
-
If the design is wrong, then it is about the design. You are trying to represent a duration, and trying to jam it in to a time field (which isn't supported and isn't the right shape for your data) is the wrong thing to do. You need to a) think about what you are trying to store and select a storage method that is…
-
My guess is that you have added the resolution field to the create and/or edit screens. You should never put the resolution field on create/edit, it should only be used in transition screens.
-
When your people visit your Jira while it is re-indexing, what error message do they see? I get one that tells me Jira is not available because it is re-indexing, it seems perfectly clear to me. Instead of messing about with a proxy page, could you suggest better text than what your people are seeing?
-
>Most of the folks who use Confluence are not doing any technical work or software development work. But they're still using Confluence, and its apps. >Could I not create one cloud instance of "Conflucne Only" for those folks? Again - this is for pure, non-technical documentation. Yes, you can. And if you go this route,…
-
Have a look at the rest of the backlog - would you think you'd be able to answer that many requests and update them regulary?
-
You'll need to talk to your people about their attempts to upload malware.
-
Yep, agree on all of that. But it does make want to ask if company-managed projects are fruit or veg ;-)
-
Three day week because we were short of electricity, hideous "fashion", generalised bogotry and being "the sick man of europe" - we in the UK will be able to experience the 70s again soon, thanks to Brexit.
-
It doesn't actually matter - Atlassian's backups are for restoring swathes of Cloud systems in case the cloud servers suffer a catastrophic failure. They are not designed or used for restoring individual systems or parts of them.
-
Peppers (including chillis), coffee, chocolate, and sweetcorn are indeed fruits, alongside tomatoes and avocados. In other news, * rhubarb is a vegetable, not a fruit * pumpkins are fruits, not vegetables * peanuts are not nuts * cauliflower, broccoli and cabbage are not vegetables * strawberries, blackberries and…
-
The project list in the create screen is generated from the list of projects that the current user has the right to create issues in, it's not the list of projects they can see. If you want to shorten the list of projects offered when creating an issue, take away the permission to create issues in the projects the user…
-
Yeah, the docs on this are really bad. "Issue role" is not a good way to talk about a project role or a dynamic role, it makes you think the roles have a direct relationship with an issue, like they are fields on an issue. They don't, and they nothing like fields. Reporter, project lead, current assignee and the others are…
-
Jira tends not to support broken processes, or at least doesn't bother to make it easy to do them. You can easily sort a search by summary if you want to - run the search, then add "order by summary" to the query, or just click on the column header to sort. Backlogs, by definition, are supposed to be sorted by rank.…
-
Team-managed projects really are very simple and lack a lot of functionality. I regularly have to say "they're not ready for real usage yet", although Atlassian are gradually adding the functions we need to them. I'm afraid the only useful answer here is "use a company-managed project instead".
-
Get her to check her email filters, it has probably gone into spam. If it's not been filtered, then ask your email servers why they haven't delivered the email, and check that the email on the account is correct and valid.
-
No. If you stop Jira, you can't run scriptrunner scripts.
-
If you have a bcc field added to Jira, one that contains people's accounts, then you can add it into the notification scheme. Jira will email the people named in a people field if you tell it to in the notification scheme.
-
Run a search for the issues you are interested in, save it as a filter and then use that filter as the inputs into dashboard gadgets that you prefer for reporting (most of them will expose the issue status to you one way or another)
-
Your use of the time field is broken, and you need to redesign so you can do it sensibly. Active objects does not have a way to support your broken design, because it is broken. You should move to storing time fields properly.
-
No, the portal is a part of a Service Managment project. Software is aimed more at developers than doing support work, so it doesn't have portals.
-
You will need to ask the administrators of ECMWF's Confluence for access to do that
-
Atlassian products have only had a "backup and restore solution" built into them for 17ish years. Could you explain what you are looking for past the "backup" option in the admin menu?
-
Atlassian Cloud is a service, not your server. If you use Cloud, you need to see it as a service, rather than something you do for your people. Stop thinking "logs", you have chosen an external service, you need to embrace "service".
-
Except that you have no idea how many people may storm it. I'm not sure one person who has access to a hundred and eleventy twelve email addresses might be a successful storm? I think you need to think through the differences between public ballot, hidden ballot and anonymous ballot (only one of them is democratic, and…
-
Yes, I've seen several clients work it out by hand, and eventually we got Atlassian to throw up a "begrudgingly recommended" method over at https://confluence.atlassian.com/jirakb/how-to-automate-backups-for-jira-cloud-applications-779160659.html
-
I like "that is not a compliment". I like Azure DevOps, but it fails to be agile because it's trying to draw in people who are pretending to be agile but aren't. At least Jira doesn't try to lie about that. And it's pretty much "Jira from 3 years ago". Anyway, yes, I also think Jira Cloud's UI is weak. I'm a howling…
-
Yes, the *technical* limit is very very much higher than the human limit - do your people find an issue with 94375 links useful? Probably not. Jira can do it, and handle it gracefully up into the thousands, but that's way way higher than your people will find useful.