Comments
-
Sorry for being so slow to get to this. The missing piece for me is how you grant access to use Jira (not projects etc, just the system) Can you tell us what you have in "Application Access"?
-
My favourite way to connect with other Atlassian users is the Atlassian user groups. Is there one near you that you could attend? There's also Summits and Team Tours, but they are more about end-user to Atlassian/Partner interaction. I'm hoping other people here will reach out to you as well, and we're trying to encourage…
-
I do not understand "Do you have any SSL certificate of Jira?" I run Jira on SSL, so I've got my certificates set up there.
-
Or possibly not at all, as the products are now diverging. Server and Data Centre are now starting to get features that will never make it to Cloud. (There's an essay on why I think this is a bad idea, but it's not for here)
-
Yes, you have to move issues through your workflow, assigning them to the person who should take responsibility for the work that needs to be done on them next. If you don't know who the assignee should be, then either assign it to someone who does, or set it unassigned and ask the right set of people to look for issues…
-
Hmm, then I'm a little confused on what you want. What you're seeing is the standard edit mode. The editor needs to be able to show you the content of macros, otherwise you can't edit them. There is no other way to edit, because you wouldn't be able to edit properly.
-
That's the issue navigator, a list (or grid) view of a filter.
-
No, this is quite a complex thing Atlassian have done (I understand why it's gone this way, but explaining that won't really help you). A project has a workflow scheme that tells it what workflows to use for the project. There is often only one workflow, but you can associate many (so you can do things like have one flow…
-
Quick filters are for drilling down into your list of issues, not sorting it. They just show and hide issues from the main board filter. The sort order remains what the main board filter says it is.
-
To simplify a workflow, you have to log in as an administrator, go to the board column configuration section and click "simplify". It's not really anything to do with workflows.
-
There is no way to restrict this.
-
To de-simplify a workflow, you create a new "workflow scheme", put the workflow into it (either as the default for all, or along with others you might want to use), and then apply it to one of the projects the board uses. That tells Jira that the board is to no longer use a simplified workflow, so your workflow now becomes…
-
Not really, there's usually little need to change field types, and most people will never do it. It's also a lot of coding for little benefit.
-
Not really a surprise - you can't do it. You will need to add a new field and remove the old.
-
The only way to limit the project selection is to make sure the user has not got "create issue" in projects. Are you sure you have "create issue" in other projects? Can you go to a project where you should be able to raise an issue and try creating there? Does it limit you to that project, or does it remain this one…
-
When you "simplify" a workflow, Jira simply creates a workflow with the current status and using an "all" into every status. This is actually just a standard workflow, there's no flag against it to say it is simplified. Once created, it is possible to de-simplify a workflow, which makes no changes at all to the workflow,…
-
It's in your https://my.atlassian.com account.
-
This has changed slightly since then - this question is three years old! Project Type now has an effect - business, service desk or software affects what you can configure for it. To make sprint appear for a Software project, create a Scrum board for it.
-
One more bracket... Change AND ((resolved >= startOfMonth()) AND (resolved < "20180208 1930")) OR ((resolved > "20180209 0600") AND (resolved <= endOfDay(-1))) To AND ( ((resolved >= startOfMonth()) AND (resolved < "20180208 1930")) OR ((resolved > "20180209 0600") AND (resolved <= endOfDay(-1))) )
-
Makes sense, but it's not going to work for a good proportion of the users, the community has a wide range of needs in doing this.
-
If the field is the same type, why bother? Just rename the field, that will be the only difference between the old and new fields.
-
Not really, it doesn't have much explanation of the phrases in your original question - the random bits about url api is unexplained. However, I can answer the bit it clarifies. You can search for issues that the current user has the right to see by searching. That's it. A search will only return issues the user can see.
-
You don't. Jira is doing the right thing here. You had a Story in a sprint, then the story is carried over to another sprint. The Story has been in both sprints, so so were the sub-tasks because they're part of it. Whether they existed or not in the first sprint is irrelevant because they are part of a Story that was in…
-
For large user bases, users in roles can be measured as faster. But it's not a great improvement, and not a reason to prefer them. (The main load is the permissions checks in there if you wanted to know) Roles however, let you delegate ownership to project admins. Rather than explain it, I'll give you a real-world example.…
-
The only thing I've seen is connectors for Google Drive - an extra panel appears in the issues and you put attachments there instead of in the internal one (which you can switch off).
-
I am sorry, I do not understand the question. Are you trying to do something with REST? Could you perform the search in the UI first and give us the JQL?
-
Which scripting add-on do you have? And what are the conditions you want to assign-to-next?
-
The reason I asked that is that the licence date calculation is sometimes a bit squiffy when you set a server to run way in the past (before 2000). But that's not the case here. Two things to try 1. Go to your my.atlassian account and get a new copy of the licence key to paste in (click the link near the end of the error…
-
The board is just a view of issues, changing the config of the board won't affect the issues. It will just change which status the board sees as "done". Your team will just see one less column on their board, they don't need to do anything!
-
Sorry, I was not clear. It doesn't actually matter whether you use Story points or Time estimates - the question is how you want them to work with the story. As an example, would you estimate a story and then reduce the estimates on it as you create sub-tasks with their own estimates? Or keep a low or zero estimate on the…