Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Git push against Devops user story/task

  1. How-to
0
Votes
Undo
  1. Bjarne Anker
    Bjarne Anker
  2. PowerBuilder
  3. Friday, 12 April 2019 06:59 AM UTC

Hi.

 

I've managed to create a Git repo in Azure Devops and have pushed all my source to it.

It's still in testing, but I want to apply this to the whole team.

But we're using DevOps as our scrum tool, and we create user stories and tasks for all out development.

In VS you can commit/push the code against a user story or task by adding "#" in front of the task number in the comment when commiting.

I tried the same in Powerbuilder, but no activity appeared on my task in DevOps (the source was updated).

 

Is there any workaround for this, and/or plans of adding such a feature?

 

 

br,

 

Bjarne Anker

Maritech Systems

Norway

  1. Git
  2. PowerBuilder (Appeon)
64-bit pborca.lib?
Window menu in MDI - list of opened sheets
Responses (3)
Bjarne Anker
Bjarne Anker Accepted Answer Pending Moderation
  1. Saturday, 13 April 2019 08:16 AM UTC
  2. PowerBuilder
  3. # 1

Hi Mike.

 

We create all the user stories and task up front, and link them to Epics and Features accordingly.

So all we have to do is to comment that number with a "#" to link the Git push to the artifact.

After that, we can create a release in PB with all object in a sprint.

The only downside is that PB only operates against "master" branch i Git, but not a big problem for us at this time.

 

Bjarne

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 12 April 2019 14:26 PM UTC
  2. PowerBuilder
  3. # 2

Hi Bjarne,

thats great that you have PB working with devops.

Do you happen to know whether you can set the next task number in your project for your user story/tasks?  and are these numbers only , or numbers letters?

I am using another scrum tool, which is great except i am unable to set the starting numbers.  These new numbers will be conflicting with old numbers from when we were using another set of tools to track change requests.     The azure devops tools seem really nice, so i was thinking we might switch over to them especially if we can get the story/task number issue solved.  

thanks,

-mike

Comment
There are no comments made yet.
Bjarne Anker
Bjarne Anker Accepted Answer Pending Moderation
  1. Friday, 12 April 2019 09:07 AM UTC
  2. PowerBuilder
  3. # 3

Hi again.

 

It turns out that Azure DevOps is able to link a commit/push to a user story or task by adding the pound sign (#) and the number of the user story/task in the comment section i PowerBuilder.

It just takes a while until it's visible in Azure DevOps.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.