I'm using the JIRA Agile plugin.
I've created a task with a few subtasks inside it and I want to assign multiple users to one subtask.
Any idea how this is possible without rebuilding JIRA from source then tinkering the code?
There is an Atlassian page that covers this topic.
The options they discuss may not match your requirements though. They seem to be focused on the situation where the users you assign to an issue are consistent and part of a group.
One option is to create a custom field of type 'group picker'. Another option is to have a user defined on JIRA that actually represents a group of users and has a mailing list email.
Related
I am a new user of confluence, I participate in an workflow in witch customer support receives bugs, I report them to a central team of developers. Now, the thing is I am trying to create a way for the customer support team to have more visibility on the issues that I report, as in to quickly find out the status of a certain issues. What I have in mind is a confluence page consisting of a table of the issues extracted from Jira but I am having trouble reaching the exact end product that I have in mind. For example is there a way for me to make a column to this table so I can add comments for some issues? or can I categorize the issues by which pack of developers are they assigned to. Mainly I want to know if there is an alternative way of going about my situation and I don't see it because of my lack of experience.
Thanks!
Rather than adding comments in Confluence I would suggest you instead add them to the Jira tickets and then display them on Confluence.
The Jira Issues macro allows you to chose the fields you display. You could, for example, add a 'Confluence comment' custom field to your Jira tickets and make sure this is shown in Confluence.
As for categorizing issues, this is best done by using filters. The approach would be as follows:
Decide what categories you want
Create a filter for each category
Use the Jira Issues macro multiple times, once for each of the filters
I was asked to separate access to a particular Jira project by component. e.g. user "a" can see issues created for component "a", but not component "b". conversely, user "b" can see issues created for component "b", but not component "a".
I know that I can limit access to a particular project to one or more users, but I was unaware of a way to filter access to one or more users by component within a Jira project.
Is there any way to limit access to one or more people to a subset (less than all components) of a project?
I did a search for a Jira plugin that might offer this functionality, but did not find what I was looking for.
N/A
N/A
I don't know if that's possible by using a component (I don't think so), but there is an alternative approach which might be sufficient as well:
You can adjust the Browse Projects permission like this:
You can grant permission to a group custom field value. Then you could choose a custom group field (create one if not available) which will be evaluated on each issue. Then, if you create an issue and add a group to this custom field in that issue, only users from that group have access to view the issue. Take care that you remove the any logged in user setting for "Browse Projects", otherwise the group custom field does not have any effect. There is also a KB article here in Jira's documentation.
The first question is what are you trying to do? Why do you want to restrict who can view issues?
Jira has Issue Security Schemes that can do this based on setting the security level according to the component, or other fields. I'd use a custom create post function
But what happens when the component is changed? Now you have to restrict editing too.
How do I share artifacts (e.g diagram and docuement) across the entire project, not just at issue level at JIRA? Something like a common area for posting information.
A couple of possibilities spring to mind.
Firstly you could use the HipChat integration. Sending messages via comments to a team HipChat group.
Another option would be to create a generic JIRA user with an email address that is a mailing list for your team. That way you can use the Mentions functionality to inform everyone of something.
More about the mentions functionality here: Atlassian - Using Mentions
Use an Epic in the project
If you are using Jira Agile you can simply create an epic (called Documentation) and house all of your documents in the epic itself or group documentation by creating subtasks in the epic to essentially create "folders". To ensure the team is seeing any changes add them all to the "watchers" list.
Use a Confluence Space
If you have access to Jira Confluence, just create a project space and create or link your documents there. Another benefit of using confluence is you can make these documents available to external customers (no need of a Jira account). To ensure the team is seeing any changes add them all to the "watchers" list.
Creating a Space
https://confluence.atlassian.com/doc/create-a-space-139463.html
Use a Project Dashboard
Use a dashboard and ask that your team pay attention to this every day. Dashboards are a great way to propagate information to distributed teams.
Customizing the Dashboard
https://confluence.atlassian.com/jira/customizing-the-dashboard-185729498.html
I would like to customize a Work Item Type in TFS to automatically set the Assignee to a particular role. For example (to compare to another Issue Tracker), in JIRA the default Assignee is the Project Lead (so that any ticket not otherwise assigned, gets automatically assigned to whatever person is designated in the role of Project Lead). Can I do something similar in TFS?
So, I realize that one difference between JIRA and TFS is that TFS doesn't (to my knowledge) have the concept of "Roles". The closest thing to that is "Groups", but unlike Roles, Groups can have multiple people (which may be the restricting factor in this problem). I know how to configure a TFS Work Item so that only a certain Group gets listed in the "Assign To" field, but I would like to go a step farther, if possible, and create a custom Group with just one member (e.g., "Issue Guru") and then set up the work item to get automatically assigned to that person.
I'm trying to replicate the Jira functionality here, and maybe there is just no good way to do it in the TFS framework. Any suggestions?
There's a Step by Step Guide on Ivan Fioravanti's Blog for enabling it.
If you are unfamiliar with customising Work Item Types, have a look at the following links (stolen from Grant Holliday's blog).
I never tried this in production but here is something I tried quickly and it seems like it could work.
You can set the default value to a Group by editing work item template in template editor.
Just select Assigned to field and add a DEFAULT rule like shown in the image below.
This will also require you to create one or more groups (one global or maybe one per project). Once you set this up you won’t have to make any updates in the future but only manage people who are in the groups.
I'd like to be able to link a subtask to 2 different user stories. Couldn't find any such option easily available in the config screens ..
Any ideas?
If you have the "Theme/Epic" field on the sub-tasks, you can add the issue keys for both of the user stories to that field (their actually labels). Then from any GreenHopper view, you can click on the hyperlinked issue-keys in the Theme/Epic field to bring up a dialog of the user story and all associated issues & sub-tasks.
You can't.
A subtask has a single parent issue.
An alternative approach is to use the issue linking feature JIRA provides and link the two stories with a single task to execute. There are a lot of benefits of doing so, as you can separate out work from specifications.
Check out a description how you can actually gear up your JIRA projects #
http://www.idalko.com/display/WIC/Separation+of+specifications+and+tasks
Francis