Comments
-
I am going to take a slightly different approach to the previous answerers. Why? What does it matter how many users you have "in" a project? This is not about answering your question, I am simply curious about the reasons it might matter to you. I completely understand "it costs us to have lots of users of the system", but…
-
That looks healthy, have you tried increasing the memory available to Jira? (If you have not, then be warned that as a Java system, it's not a good idea to go up in huge chunks. Don't take an 8Gb Jira up to 16Gb, add 1-2 Gb at most in one step)
-
Welcome to the Atlassian Community! I would guess that a moderator has moved your post(s) because it was not in line with the posting guidelines. The TLDR of the guidelines is that they ask people to be constructive and, ideally friendly, but certainly not confrontational. To my mind, in this case, that means: When…
-
That's quite an interesting one. The basics of the story are that you've done exactly the right thing, and it should not affect your velocity. There are, of course, two important points in a sprint - starting a sprint says "we are saying we will deliver these issues", and it gets stamped with the estimate of all the issues…
-
This is likely to be being done by the template or blueprint people are using to create the pages. You should be able to change or remove it from the template.
-
Welcome to the Atlassian Community! You are going to need to talk to the administrators of your Confluence system. The community here has no sight or knowledge of your system.
-
Bother, I missed the link in my previous posting, sorry. It's worth looking at all the options. As a partner, I should not really be making any recommendations other than a) my own products, or b) my honest experiences which clearly push an option to the top of the list. But on backups, Adaptavist don't have a product. I…
-
Welcome to the Atlassian Community! Atlassian does not do telephone sales or support (except for large premium or enterprise systems with many many users, and even then, they ask you to raise support calls). You'll need to raise a support request and wait for them to ask you about your preferred way for them to talk to…
-
Eh? As talked about several times in this question, you raise them in jira.atlassian.com (and support.atlassian.com/support will guide you there if you go down that route). If you're redirected to community, that means you are not running a supported system, so you can't raise support cases. In this case, ask the Community…
-
I'm afraid you'll need to script or automate that. Or just rename the field to whatever you want to call it.
-
If you visit admin -> issues -> status, you will get the list of status, each one with a link that pops the list of workflows it is used in. I'm afraid you will then need to manually cross-reference that with the admin -> workflows list that tells you what projects are using a workflow.
-
Welcome to the Atlassian Community! https://library.adaptavist.com/entity/populate-a-scripted-field-with-the-sum-of-all-values-added-or-updated-in-a-number-field does the basics of what you need. But, the field you are reading the values from will need to be calculated, not just read. I'm assuming your source field is a…
-
That's what I would assume as well - an admin has (probably accidentally) imported a CSV file which included a "description" column and selected "create new field" instead of "map to system description field" If that's the case, then go to Admin -> Custom Fields, and look through the list, you should find that there is one…
-
Story points are mostly intended to be used in Scrum teams, to estimate relative complexity or effort required to deal with a story or issue. They feed into the sprint metrics and give you the team's "velocity" as they complete stories. Sub-tasks are fragments of their parents, not separate sprint items. They get completed…
-
I'm afraid this is wrong. JQL does not have any way to compare two fields. You can indeed do it in an automation function, but that's not what the question was about.
-
Welcome to the Atlassian Community! JSM does not do it directly in Cloud, it uses Atlassian accounts (individual or tied into a Google account) or Atlassian Access as the user directory. Atlassian Access can be hooked up to Azure amongst other user systems to provide the user accounts, and that fully supports SSO.
-
Sorry, I didn't really explain this too well. Your question was clear. This property does not exist for other fields. You can't use jira.field.customfield_123.exclude for example - the function only supports the resolution field.
-
The best way to do this is with "conditions" in the workflow. If, for example, you have a field with options of red, green, and blue, then you set up your workflow so that you have the transitions * To-do -> in-progress with red team * To-do -> in-progress with green or blue team Then you can put a condition on the first…
-
There is no way to do this - the closest you can get is to block all editing of the issue using a workflow property
-
Welcome to the Atlassian Community! This sounds like a design phase is part of the process of getting a story done. If something is a procedural step, the best place to do it is in the workflow. In a very simple case, I would start by having a workflow that goes To-do -> needs design -> in design -> needs development ->…
-
There are a couple of marketplace apps that can automate the use of Jira's backup systems and be set up to do it regularly. Have a skim of https://marketplace.atlassian.com/search?hosting=cloud&query=backup
-
Assignee is "the one person currently responsible for getting this issue dealt with", it should never be a group or hold more than one person - that will always fail you in real life. Your teams will all eventually get it wrong and start playing blame games. However, there's nothing wrong with having extra fields that say…
-
If you stop paying for and using a Cloud system, Atlassian will shut it down. If it remains inactive, they will delete, and remove it from the backup cycles (I have an unreliable memory that if you don't re-activate it within 150-ish days, then you'll lose the whole lot)
-
There is another complexity with Confluence. Although it is licenced separately to the Jira applications there's a lot of types of user licence, and you can have different levels. For example: * 25 business using Jira Work Management * 50 developers on Jira Software * 5 helpdesk agents running the Jira Service Management,…
-
That will work as you describe, but only for the issues behind the requests. Your customers will still be able to see, and create, requests of any type. They just won't be able to see the issues the agents are working with. But most customers don't get to see the underlying issues anyway.
-
Welcome to the Atlassian Community! I would not "import" cards from multiple projects, I'm not sure it would work for you. There are three ways you could import * move the issues into the master project - this would remove them from their current project, which is probably not going to work for the people in those projects…
-
It's not about publication, Atlassian just don't have SLAs for the standard tier. They don't support the free (or starter) tiers at all. Although we can always ask them nicely here. They do not store across AWS regions, they store in the one nearest the place that you were using when you signed up. You can grab a backup…
-
Welcome to the Atlassian Community! Both. The bug (in my opinion) is that the error message is a bit unhelpful - it should be saying "there is already a repo with this name, but it is not one you have any access to view".
-
Welcome to the Atlassian Community! There is no way to re-arrange this view, the issue you've found is the request for it, and still holds.
-
The workflows are tied to the issue type - if you select and issue type of X in project Y, all issues of that type in that project will follow the workflow Z It's not directly the workflow that was the problem, it's the project/issue-type associated to the workflow. The thing that does not make sense to me in this scenario…