Comments
-
I'm afraid you can't grant that - to see groups, you need to be an administrator
-
I've been using Jira for years, and #4 still bites me when I'm testing stuff :-)
-
Check that the fields are 1. On the right screens (You probably have done that, as you've added them to every screen, but check anyway - the screen you are looking at is strictly the VIEW screen for the issue, so it's worth checking through the "issue type screen scheme") 2. Not "hidden" in the project's "field…
-
That's why I was asking for what you see on move. What happens when you click "move" on the issue? What is the error message and where is it? Actually, you now say you can't move it, so you can't have got an error message, so I'm even more confused.
-
I'd like to see the move error, not the create. the create is trying to stop you from losing data already entered (or defaulted) - if you changed to a new issue type with a different config here, it has to lose all entered data. The move is a different story.
-
You won't get that sort of error when you move an issue - could you show us exactly where it goes wrong when you use "move"?
-
This sounds like you are trying to change an issue type using the simple issue type field. You can only do that if the source and target issue types both have the same field configurations and context, and the same workflow. You say the workflow is different, so there's the answer. You'll need to use the "move issue"…
-
I don't usually like to answer "will Atlassian support X in the future" questions, because I can't be 100% sure that they will not change their mind. On this one though, I know it's a "No". There is no point coding for a browser that is at the end of its supportable life and won't be supported by MS at all in 10 months.…
-
Your instincts are correct - you can't change them on Cloud.
-
The new licenses will be compatible with all versions, so don't worry about the order too much. However, I'd be strongly tempted to do them first for one reason - you can't upgrade past the end of the license. For example, if your license ended yesterday, and Atlassian release Jira 5.2 tomorrow, you can't upgrade to it.…
-
No. The issue key is determined by the project key. You'd have to rewrite a lot of Jira and it's plugins to change that.
-
Cofluence is primarily a wiki, which means each page is a block of text. It doesn't particularly have "fields". Could you explain what you mean by "fields"?
-
Yet again. Admin -> General Configuration -> Advanced
-
No, I described the way to find the property string you needed to amend. "duedate" is the key of the "Due Date" field, as I said earlier. Most of the system fields have ids that are close to their actual English name
-
That page is little more than a big pile of property strings. Try ctrl-f in the browser and look for sub
-
Sorry, what? You can't find a string on a page?
-
(or on the header line, I can't remember the exact layout, admin changes a lot)
-
Sorry, I got that wrong. Search for "general configuration" and look for the advanced button at the bottom.
-
Try the search function instead - press g then g again, and type "advanced" into the search box.
-
The system fields have different names, like duedate 6.3 definitely has the option under Admin -> General -> Advanced, so I'm not sure what you're getting.
-
What version of JIRA are you on? (the field is called duedate when you find it)
-
https://confluence.atlassian.com/jira/how-to-display-custom-field-of-the-sub-task-in-the-parent-issue-screen-163939652.html should still work in 6 and 7
-
What do you get when you try to use confluence? What is the url you end up on? What's the error message? What does your log file say?
-
You might want to look at https://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand to get started on many of those answers. It's the one we all point at when someone asks about plugins for OnDemand, but I think it'll answer all of yours if you follow some of the links in there (although, I'm…
-
A variation on "custom field with previous status" is to use a condition that looks at "previous status".As usual, I'd do that in the Script Runner, but the Jira Misc Workflow Extensions add-on also provides one of these off-the-shelf. There may be other add-ons that do it too.
-
That's roughly what I was going to say - the clause looks like "cf ~ value1 OR cf ~ value2" to me. Or, if it really is an exact phrase, the ~ operator will get immensely close and try to pick up values that are mistyped, which is probably better than a precise match when looking at a raw text field. Maybe I've…
-
No, it arrived in 4.3. You need to upgrade.
-
There does not seem to be a question here. Yes you can make fields global, or tie them to individual projects/issue-types. You can change this context later if you need to. I'm not sure what else you are looking for.
-
You'll have to remove them from all the rules that notifications use to say who to send email to.
-
Use the "browse" permission in the project, and allow it for the group "anyone" (it's not a real group, it just means "let everyone do this without logging in). Be aware that this opens up your project for anyone who can see your project, and they'll be totally anonymous, so be careful not to grant any other permissions to…