Comments
-
Good point, I was thinking that you'd use Confluence to replace document objects, as that's by far the best way to use it. Network Share and Sharepoint handle document objects, but Confluence handles pages, and it's not intended to be a document management system (it's not a lot better than a file share for that - you get…
-
It's a business decision really. For stuff that does not need to be tracked in any way, and you don't care if multiple people could make a mess of it with no history and little in the way of access control or search facilities, you can use network storage (basically, don't. Network storage gives you the ability to share…
-
None. A menu doesn't know where you want to place it. Try highlighting some text and use the context menu there. Should be a speech bubble
-
Look at the bottom of a Confluence page for the version (or system information in the admin section if your admins have removed the versions). The latest version is 5.9, I think the comments arrived in 5.7, but possibly earlier
-
My guess is that you are using an older version of Confluence that doesn't have in-line comments
-
Er, I already pointed out that inline comments are there.
-
A wiki is very different to a word processer and basically won't do this in the same way. So yes, "you should be doing something completely different" But, not that different... To answer your points: * Recent versions of Confluence have inline comments, and discussions in place after them * Look at the page history *…
-
No, the add-ons will continue to work as before (if they have software specific functions, those will spring to life too).
-
The way I think of it is that all add-ons get installed in Core. There are a (very small, but growing) handful that require that Software or Service Desk are installed, but that's because they are intended to enhance those particular applications. At the moment, everyone with Core gets to use the add-ons, no matter what…
-
So what type *exactly* are the stories? What else do the missing ones have in common?
-
Technical tasks are often defined as sub-tasks. Could you look at the list of issue types and check that your "technical tasks" and "stories" are *definitely NOT* sub-task types?
-
I assume you mean "Scrum board", as Kanban boards do not have "plan mode". Could you do a little analysis on what the missing issues have in common? Are they all the same type of issue (or types)? Specifically, are they all sub-task types (which won't show in planning mode because they're not needed for planning)? Or do…
-
You'll need code (Assuming you don't want to do it with sub-tasks). Fortunately, people have written it already - have a look in the marketplace for "checklist" add-ons.
-
No, as I said, the code in Jira only handles create permission at a project level.
-
There are some hacky ways to stop them, but I've only seen them implemented in the core of Jira and not Greenhopper at all, and they're not particularly friendly or elegant. The nicer ones use a bit of javascript to read the users profile and delete options from the drop-downs, but I've not done it myself (and I've not…
-
No, Jira has a flat, simple "Do you have create issue rights in this project" rule. It's not done at an issue type level. You could set up separate projects to delimit the types, but that's about it.
-
I'd say define the processes you want to end up with and build workflows that match them in JIRA. That will give you an end-point, and you can then look at your data in AT and decide what to transfer and how. I can't recommend add-ons for waterfall - that's far too vague a description of what your process is going to be…
-
Why? It's different software, and hacking it to look like something else is a lot of effort for no probably reward.
-
>It looks like I could create a new permission scheme Yes >and exclude this group from the "Create Issue" permission setting No. As you say, it's all about inclusion, not exclusion. I would also do it entirely with roles, rather than groups, so you can reuse the permission scheme, AND delegate the maintenance to the…
-
Don't give them "create issue" in the projects, but still let them have "comment" It's all in the permission schemes, as Tom's link says.
-
You need to accept one of the answers (should be a tick to the left of them all)
-
There's nothing to stop you defining read-only access to the project and then a security level that is identical to it (or a sub-set of those who can read only)
-
Best guess is that you have a broken or faulty post-function on the issue creation
-
I don't know what you mean by "showing back", but being unable to close them means either * the conditions on the workflow actions do not allow it * there is no transition to closed from their current state * You have a broken database - try the integrity checker workflow checks Note that the indexing does not affect the…
-
You need to talk to your administrators - you're asking for help in a forum that is for end-users of Atlassian software, which is fine as you are using Atlassian stuff. But you're asking about project or organisation things that are specific to your organisation. We're not your administrators or colleagues, we don't know…
-
They're on a Windows box - no iptables installed by default. Might as well use IIS or Apache, as you're going to have to install something there to make it work.
-
Yes, that's been written by someone who followed Atlassian's instructions on using IIS to do it, as I mentioned.
-
The document Jing Hwa has pointed to covers it all. Install apache, set it up as instructed. It is actually generic - it's not just Confluence you would do this for, but any web application you want to relocate. We can't hold your hand through this - you need to follow the documentation and learn for yourself - if you…
-
If it's a "fresh install", then I suspect you have little or no data to search yet. If you do have data, then I'd try re-indexing JIRA and then reading the log file to see what happens during the index process and then when you try a search
-
Oops. Sorry, Petar beat me to it.