Comments
-
Not installed, just spun up. You don't have to think about any of this. If you want to move off Cloud, yes, you can download your data in a format suitable for importing into your own Server installs.
-
I'm afraid it doesn't matter what you think. The mail server is being given invalid credentials and Jira does not do anything "clever" with them when it tries to use them, it literally sends exactly what you enter. Whatever you are putting in is not valid. It may be that gmail has been configured not to accept login from…
-
Yeah, videos vary between mostly useless and plain wrong for instructing Atlassian admins. All you need to do is read the permission scheme and match the rules for users correctly. Look at the permissions for ABC and XYZ. Make sure that ABC_group matches the permission for Browse project in ABC, and does NOT in XYZ. Also…
-
Those three are system fields which will always appear on issue view unless you hide them in the field configuration. For issue name, it needs to be added to the issue edit screen
-
That suggests the add-on has a bug, and is invalid. You'll need to work out exactly what [object Object] is and get the authors to fix it.
-
There is no way to do this directly. You can have users who can create, but not edit, but this is a project permission that means they can't edit any issues at all. You could grant them edit and set permissions in the workflow (with workflow properties on status), but this will not be based on the reporter, as you can't…
-
Then, I'm afraid, you are giving it the wrong credentials.
-
Check who the permission schemes grants "assign" and "assignable user" to. Make sure your users match what you want - they sound like they need both.
-
In another post, you seem to have picked up 5 year old docs for SR for Jira Server. ScriptRunner for Cloud is a lot younger than that. Have a run through http://scriptrunner-docs.connect.adaptavist.com/jiracloud/post-functions.html#_fast_track_transition_issue
-
You will need an add-on, one that can provide a "listener" that can watch for changes to the issue - when it detects a change/addition/removal of a component, it can set the security level. This could be quite horrid for the users though, as they might change a component and have their issue vanish because they're not in…
-
I do not think I understand the question, but I think you are looking for Story points > 0 or QA Story points > 0
-
Champions have seen the same and poked Atlassian about it. Try again soon!
-
The searcher also needs to be able to return a known list type data set - one with known boundaries (e.g. a list of countries, colours, people, etc). You can do this for select type fields, but numbers, dates, and plain text cannot, as the data range is effectively infinite.
-
It's the Epic Link field on the stories, coupled with the Epic Name field on the Epic.
-
Create a new screen, with a name like "my resolve screen", then go into the workflow (in your screenshot), swap to the diagram view and find the "done" transition. Click on that and add your new screen to it, and then go to the post-functions and remove the one that says "set resolution to done"
-
The code behind the add-on looks specifically at the resolution field. You would need to change the code to look at status instead and recompile the add-on, it's not as simple as just amending some xml.
-
No, disabling the add-on does it for all users and file types.
-
I'm not sure what you mean by "program screen data" - I get the tempo data back when I try it.
-
I have a strong opinion that differs from yours, and I offer evidence to support it. Resorting to name calling instead of evidence just tells me that you know you're wrong, as it's a argumentum ad hominem. Finally, I'm not an Atlassian, I'm an admin of their software who has spent far too much time with broken searches and…
-
I'd want to look at the Jira application log <jira-home>/logs/atlassian-jira.log and look at turning the logging levels up. That should tell you if the system is getting the emails and failing to process them into comments, and why they're going wrong. It may also tell you that it's not getting them at all. My suspicion is…
-
Nope, definitely no bug. Assignable user permission controls who can be assigned to an issue. Assign to permission controls who can assign issues. This gives you four possible options for any given user, and massive flexibility in choosing who can do what
-
There is no "resolve" transition in your workflow, or, if there is, there is a condition on it that prevents you from using it. Have a look at your workflow to see what it's doing.
-
I do work in several environments that use labels. I've spent over 20 years in these environments. I have yet to find one where spaces in labels work, and I've been specifically commissioned to write code to expunge them, because they do not work. At all. Your screenshot and explanation is useful to see how you're…
-
You would need to hack the core Jira code. It is currently built to take people to their preferred dashboard. You can't break that with an add-on. Unless your add-on is a brilliant replacement for the user's own personally customised dashboards that work for them, you really don't want to do this anyway.
-
No. If an email arrives, JSD processes it. It doesn't care where the mail is from. Either your .mil users do not have the rights to update issues, or your mail servers are dropping their mails.
-
But you can't find anything you want to unless you know exactly what you are looking for. You have four labels in your screenshot, of which Two of them are useless because no-on cares about "xxx yyy zzz". They DO care about keyboard-navigation, names, roles and values. The third is even more dreadful. What does "Level A"…
-
That is what they will see. The status is that, so that's what they get. Could you explain what is not looking right here?
-
Given a 2 year old post against a system that has significant releases every 3-6 weeks, I don't think that's a surprise. The docs move on. But the original answer is still right, as is the idea in the doc pointed to - have a look at the Connect Developer docs.
-
I'd ask them for support. That could well lead you back here to the community, but there are no tags or anything here to help them find your question. If you follow their support process and do land back here, it should pre-populate the tags at least.
-
The board only considers the far right column to be "done". You need the issues to be in the last column when you close the sprint.