Comments
-
Ok, you're getting close. On the first screenshot, you have highlighted the system Priority field - that will appear if it is set, even if you have removed it from screens so users don't set it. Your second screenshot shows an issue where it has not been set. If you want, you can surround that with an "if" to hide it. Both…
-
If you go to Admin -> Issues -> Status, it lists all of them, along with a link to how many workflows a status is used in. To flip in-progress-eng back, just rename it, then use the list of status to find out where you need to associate a different status for it.
-
The error you are seeing in the log implies there is no parent issue to attach the sub-task to, which would only happen if the post-function were running on an issue that was not a parent type.
-
Whichever ones you set. Look at your workflow transitions. They all have a "post function" for "Fire event". The events named correspond to lines in your notification scheme. You can change the events being fired to anything you want (inluding your own events - if you add new events to the system, they will become…
-
There's a block in the middle of your question to expand on to provide a couple of possible answers. >Now we want a solution such that external customers can interact with us on different internal projects but we don't want to give access to internal Jira server. These answers requre users to have some access to your…
-
No, you will not be able to renew after a number of renewals. You're also breaking the law if you bypass the limitation.
-
No, the Atlassian licence is users on a service, not "user can use every Atlassian system everywhere"
-
You say "it's not enough", which implies that you've looked at Insight and found it lacking. It is currently the most tightly integrated with and best Asset system for JIRA, so you'll need to do some more thinking. I can't begin to tell you about other systems because I don't know: * What else you need. The stuff Insight…
-
Go to user management and create new accounts for them.
-
Yes, that's what option 1 was. You'll need to add the people from Organisation2 into your user directory for the Confluence you want them to see, then add them to the space you want to share.
-
Ah, I was afraid of that. Without GA, I think you're stuck, and need to get in touch with support.
-
There's a couple of options. First, have a space that is visible to the users you set up for those organisations and individuals. You'll need to check over your existing spaces to ensure that you do not accidentally grant them access to other spaces. (For example, if you use "confluence users" to say "can see space" and…
-
I know I'm not being "helpful" here, but your approach to this is pretty much broken, and it is always worth questioning it when we see that. If you insist on persuing it badly though, then the problem is in your line getPropertySet("GROUP") != 'G1' This "get" does not return a simple string, it returns a whole property…
-
Your 2FA on your 'phone should have been attached to the number, albeit with a key that you may have destroyed. You should be able to re-do the 2FA on the phone if the number is the same. If not, then you'll need to get in touch with support over at https://support.atlassian.com
-
Yes, that last paragraph is not well-written, sorry. One good thing about using Confluence is that you can separate out content and layout. Imagine you have a block of text with a load of formatting (not horribly complex formatting that Word processors are capable of, but good enough to present to users for docs, including…
-
It's absolutely not the simplest way to do it. You still have to identify your users and then set a property to do it. Why not simply set a group instead? Also, this makes me suspect that you're setting the user properties in a way that is wrong, as there's no easy way to do it reliably, and if you were doing it the…
-
I don't understand why you are doing it this way. It's clumsy, frail and not transparent. You're doing a lot of work to do something JIRA does off-the-shelf in a really simple way. Put your users into groups. Use the permissions to say "only users in group 1 can create issues".
-
Go to the Scrum board you have defined and look at the reports tab. Plain JIRA (JIRA Core, or older JIRAs without the Agile add-on) doesn't have support for Scrum, and hence doesn't have a burndown.
-
Also, I forgot to pick up the last bit. Templates can give your users a great guide to the layout you want them to use, freeing them up to actually get on and write content. You certainly should be able to knock up a template with the layout you describe. It's pretty close to the layout I write most of my stuff in (when my…
-
The docs are almost entirely Confluence, but they use the Scroll Viewport add-on to change the look a bit. It's worth a try if you need different views on to your docs. That doesn't really answer your question about templates, but I am trying to say that you won't quite get an Atlassian style doc out of Confluence +…
-
I think you have not taken account of the resolution The resolution field needs to be set for (the main part of) JIRA to see the issue as "resolved", and hence not appear in things like the "my open issues". Take a look at your workflow, and look at the two sets of transitions: * For any transition that is from a status…
-
Ah, sorry, I was not clear. I mean the actual logs, not the semi-useless stuff Windows pretends is a log. What do the application logs say? You need to look in <jira home>/logs - probably for the atlassian-jira.log . The simple experiment is to be "tailing" the log (i.e. reading it live) as someone tries oneof the logins…
-
Make sure the "assignee" field is on the "Edit screen" for the issue. The easy way to do this is go to the issue view (not card, or quick view, bu the full view on https://yourcompany.com/jira/browse/ABC-123 ) and click Edit. On the screen that pops up, at the top right, use "where's my field" - it will tell you why the…
-
The error in there tells me the velocity you have written is not right - have a look in the file you've edited for the lines it's complaining about.
-
No, it's not schemes. It is contexts (schemes have another different meaning, do not mix them up with contexts) You can create several contexts each with one or many projects in them.
-
Definitely a support call, I can't diagnose what's going on with this.
-
Go to the list of custom fields, find the field, click configure. You can add contexts to it with different lists of values for different projects OR different issue types.
-
It sounds like a bug, but I can't replicate it. When I go to a scrum board with shared issues, I get the scrum backlog. What version are you on?
-
Hmm, that doesn't look right. Is that display what you get when you go to the Scrum board via "manage boards"?
-
No, it's there. It's more that your browser doesn't like it because it's not logged in. Try using a curl command to test it - https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-version-2-tutorial