How to assign tasks in Bugzilla? - eclipse

i intend to use bugzilla eclipse plugin for collaborating in my project
we are a team working together in one project
and i was wondering how can i assign task to another colleague in the project using bugzilla
please guide me since, tutorials are very brief.

Browse to the issue, type in your colleague's email in the Assignee field, click Save Changes.

Related

TFS Eclipse plugin change default Check in Action to Associate

I have Eclipse Neon with TFS plugin
When I check pending change and I relate to work item
The problem is that the Check in Action by default is Resolve and not Associate
How do I change the default?
All I found online is about visual studio which didn't help me.
(Registry not worked HKEY_CURRENT_USER\Software\Microsoft\VisualStudio**11.0**\TeamFoundation\SourceControl\Behavior #ResolveAsDefaultCheckinAction = "False")
Unfortunately, this could not be achieved in team explorer everywhere(TFS Eclipse plugin) for now.
As a workaround, you could edit the Work Item Template definition for the types of work items you are using (Bug, Task, etc.). Then remove the Check-In Action from the Work Item Template (WIT). Once the WITs have been updated into your team project this will be available for all users. Now when you add a related work item, the only option available is Associate. However, this solution has some pros and cons. Below is a few to consider:
Pros
This change only has to be made the Team Project and nothing has to be done on the clients.
If your team not resolve the work item, removing this option is not a big deal.
Cons
This would need to be applied to all current Team Projects and would
need to update the Process Template for future Team Projects.
This removes the Resolve option for users, so there is no way to perform this action anymore.
More details about how to remove resolve option, please refer DaveShaw's answer in this question: How to disable auto done status for task in checkin

Why Mylyn is not getting issues from GitHub?

I recently started to use GitHub Mylyn connector for Eclipse and I have it working, I create new tasks and I can see them in Eclipse and GitHub.
The problem is when me or someone else create an Issue on GitHub I can't see it on Eclipse. I have done this and configured Mylyn on that way as you can see in the image:
But as you can see under "Bugs and Enhancements" I have nothing and here I actually have one issues, so, why don't they appear? Is something to do with the fields Assigned to and Mentioning ? I have filled both with my GitHub username, then only one but with no results.
I was also having same problem. The problem here is that the Labels which are checked have And relationship rather than Or relationship, i.e if you check both bug and enhancement only the tasks that are labelled both bug and enhancements will show up there.
So, I think it will work if create separate query for enhancements and bugs.

Source Control in Lotus Domino Designer

We have been using Domino on a large project for years without any real source-control (other-than server backups). So, I was rather pleased when I noted the latest Designer 8.5.3 has potential integration with SVN.
I was unable get SVN working just by following the original instructions for as already noted on Stackoverflow the update sites have moved. The solution posted on OpenNTF, only half worked, with Domino still croaking at GEF, Mylyn and some other missing plugins. After finding and installing them, I still do not seem to have source-control integration.
What I have now is the ability to create on-disk projects but I do not seem to have any source-control features. I was expecting to see menu items for commit, update, revert …etc – is this how it works in Domino?
I can of course create a repository to commit the on-disk project to but I was hoping for integration inside of Domino. Whilst having years of experience in programming I’m a novice with Eclipse. I assume that I’ve done something wrong with installing the plugins? it was certainly a complicated process trying track down missing plugins.
Has anyone tried this recently and succeeded? What files do I need to install, setting tweak, …etc, to ensure this works? I’m happy to install my Designer fresh and follow a list of instructions.
Also, am I understanding how the integration works? Will I get command integration within Designer or do I have to work separately with the on-disk projects? I was really hoping for this be easy to integrate into normal workflow so I can convert the team to using it (adding too many extra or complicated steps is unlikely to create a conversion).
I posted a screenshot of my installed plugins in case this is helpful.
Mercurial? As an aside, has anyone used Mercurial instead of SVN with Designer? I would rather use Hg as I’m using this for related Dojo projects and will be easier for the team to use one system. However, I will settle for SVN as any source-control is better than non.
Update: This is answer is now out-of-date. It is useful in that it should point users in the right direction but it isn't really a working answer anymore. I no-longer develop on Lotus Notes so I cannot update it to a current solution.
I managed to figure this out eventually but will post the solution, just in case anyone else has the same trouble.
The answer by Per Henrik Lausten was very helpful as it showed me the route to follow through the menus. The main problem is that I'm not used to how Eclipse works so I didn't realise you had to go to the "Team" menu and "Share Project" after creating the on-disk project. When I did this I discovered that both SVN and CVS were already available.
I found that SVN did not like the file:// protocol (perhaps a windows issue?) Since, I could not arrange for an SVN server on our network, I decided to go down the Mercurial route. This was better for us as our other projects are stored in Mercurial.
Setting-up Mercurial with Lotus Designer 8.5.3:
In Domino preference (File -> Preferences), set: Enable Eclipse Plugins in the Domino Designer section to ticked.
Also in the preferences set: Use Binary DXL for source control operations to unticked (File -> Preferences, Domino Designer -> Source Control). Without this ticked I was not getting text for my Lotusscript agents and it would be difficult to compare changes.
Go to File -> Application -> Install:
Select Search for new features to install and click Next.
Click Add Remote Location button
Add the url: http://mercurialeclipse.eclipselabs.org.codespot.com/hg.wiki/update_site/stable/ and give it a suitable name
Once you've added this, ensure it is ticked in the location list and click Finish
Design will then search for updates and give you a list. Untick "Only show latest version of a feature per update site"
Tick MercurialEclipse 1.6 from MercurialEclipse Stable Releaes. I found that the latest version does not work, however a previous Stackoverflow conversation indicates that version 1.6 does work.
Click finish and allow it to install.
You will be asked to approve various plugins and then to restart.
MercurialEclipse, should now be installed!
To start using Mercurial with a Domino Application:
Right-click the application in the Applications tab, select: Team Development -> Set Up Source Control for this Application.
Give the project a name and choose a location for the project to be stored.
Designer will then do a DXL export of the database to your chosen location. A Navigator tab will appear next to Applications.
Right-click your new disk-project in the Navigator and select: Team -> Share Project...
Select Mercurial from the Repository types and allow Designer to create the repository.
You should now have access to various Mercurial functions via the Team menu. (You need to make your first commit.
When you make changes you want to commit to source-control, you need to:
Right-click the application and choose: Team Development -> Sync with on disk project...
Go to the Navigator tab and right-click your on-disk project, selecting team.
Most of the above steps should be obvious but decided to post full details in case anyone struggled like I did with Eclipse and how to use it properly. Once I figured it out, it really was quite easy.
Keith Strickland has created a series of blog posts on using source control with DDE. They might help you:
Keith Strickland: source control in DDE part
1: http://www.keithstric.com/A55BAC/keithstric.nsf/default.xsp?documentId=B236F39DEAF6C52F85257A72001157BF
Keith Strickland: source control in DDE part
2: http://www.keithstric.com/A55BAC/keithstric.nsf/default.xsp?documentId=B5D76A6DA163DCB585257A7C004802B6
Keith Strickland: source control in DDE part
3: http://www.keithstric.com/A55BAC/keithstric.nsf/default.xsp?documentId=C2C46D278948A24985257A7D0055D25E

Github Issues as Tasks in Mylyn ( Push task works, pull issues(Tasks) doesn't )

So I've recently started using Mylyn at my company, love it personally and works great with Jira. However now I'm trying to get it working on Github for personal projects that I work on with several other people.
I'm using Eclipse Juno with the Github connector and added the repository information. When I go create a task, it correctly does so and does pull the tags that I have configured correctly, so I know it has good connectivity both ways. When I save the task in Mylyn it will show up on Github just fine.
The problem is, I need access to issues that others create on Github, but when I create a Query in Mylyn and name it ( Say "All Bugs" ), then choose the bug labels and hit finish it shows the query in the Task view, however it is empty and never retrieves the list of Issues from Github. I know their there, it's just not showing them in Mylyn, and Mylyn isn't throwing any errors.
I've also tried a Query with all the above and "Mention" field with my name( just in case the blank fields were messing with the query ) however that didn't work either.
One thing to note, I'm using this on a Private repo, but doing searching( and as evidence that I can fetch labels and push issues ) I don't think private Vs public repos are an issue here.
Really hope someone can lend a hand. Thanks
#TheKojuEffect answered this one for me here:
Why Mylyn is not getting issues from GitHub?
Basically, if you select more than one label in your query in Eclipse, the query will only pull the issues with ALL of those labels (Logical AND, as opposed to the OR that I was expecting). Create a query for each of the issue labels you'd like to see.
The best approach to this is to open a bug report against Github connector for Mylyn.

Share the eclipse search result/ query

I just want to know if the search result in eclipse search view can be shared with fellow team mate as it is.
I perform a search and delete few unwanted entries and then send it to him/ her
The other person shall be able to view it exactly same manner in the search view.
Is there a way to do this?
The will be very helpful for me
You should be looking at the Mylyn project (http://eclipse.org/mylyn).
This project allows you to create tasks and send them to co-workers through a task repository (such as bugzilla, jira, or most major issue trackers). Attached to these tasks are "contexts", which associate code elements (methods, fields, classes, etc) with the task.
Here is what you would need to do:
Install mylyn (you and all co-workers)
Install the proper connector for your issue tracker (most major issue trackers have one). If you are not using an issue tracker, then you can still import and export tasks as files, but it is less easy to do, and I'd recommend using an issue tracker anyway.
Now add the task repository to your Eclipse. This is the way that mylyn speaks to your issue tracker. It allows you to create issues, bug reports, tasks, etc, from within Eclipse.
With this set up, you can now create a task associated with a task repository and activate it. You can add the desired program elements to your task by right clicking -> Mark as Landmark.
Once you have your task context complete, you can then attach the context to the remote repository (essentially attaching a zip file to the issue in your issue tracker). Other users can then retrieve the context and immediately start working with the context that you created.
It is really a great way to work when you need to share information about specific features in the code to other people on the project.